Re: VN bug or pilot error ?
On 22-Jan-01 Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, John Hay > write > s: >>> >>> But while you're at it, migrate to md(4) instead of vn(4), it does >>> vn(4) will be deprecated RSN. mdconfig(8) configures the md(4) devices >>> >> >>So why not change the release process to use md instead of vn, so that >>we can make sure it works before vn is axed? > > I will do, as soon as I have time... If you work up a patch, I can test it in about 4-6 hours time.. -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/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: buildworld failed and PERL_THREADED=true dead...
Hi I see no perl failure below... M > Hello. > I tried make buildworld after cvsuped my source and it failed in perl > area. > I remove PERL_THREADED=true and tried again and it failed. > > ===> usr.bin/kdump > cc -O -pipe -march=pentium -I/usr/src/usr.bin/kdump/../ktrace >-I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c >/usr/src/usr.bin/kdump/kdump.c > cc -O -pipe -march=pentium -I/usr/src/usr.bin/kdump/../ktrace >-I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c >/usr/src/usr.bin/kdump/../ktrace/subr.c > gzip -cn /usr/src/usr.bin/kdump/kdump.1 > kdump.1.gz > cc -O -pipe -march=pentium -I/usr/src/usr.bin/kdump/../ktrace >-I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c ioctl.c > In file included from ioctl.c:99: > /usr/obj/usr/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined > /usr/obj/usr/src/i386/usr/include/pccard/cardinfo.h:81: warning: this is the >location of the previous definition > In file included from ioctl.c:51: > /usr/obj/usr/src/i386/usr/include/machine/i4b_rbch_ioctl.h:45: `TELNO_MAX' >undeclared here (not in a function) > ioctl.c: In function `ioctlname': > ioctl.c:693: invalid use of `restrict' > ioctl.c:693: sizeof applied to an incomplete type > *** Error code 1 > 1 error > *** Error code 2 > > FreeBSD 5.0-CURRENT #0: Sat Jan 13 22:57:43 MSK 2001 > > Any idea? > -- > > Rgdz,/"\ > Sergey Osokin aka oZZ, \ / ASCII RIBBON CAMPAIGN > [EMAIL PROTECTED]X AGAINST HTML MAIL > http://freebsd.org.ru/~osa/ / \ > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
about ppp..
One of my current machines here are running PPPoE.. for some reason, it will some times become extramly lag of its PPPoE connection. (for example, from 25ns ping time become 2500ns ping time). And will back to normal in few mins.. However, i do not see the same problem on my 4.2 stable system. is this a known problem or just me? plz help! thx.. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
buildworld failed with sysinstall
Hello, 'make buildworld' failed while trying to comple sysinstall: cc -O -pipe -Wall -I/usr/src/usr.sbin/sysinstall/../../gnu/lib/libdialog -I. -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/sysinstall/keymap.c In file included from /usr/src/usr.sbin/sysinstall/keymap.c:40: keymap.h:3239: `keymap_us_pc_ctrl' undeclared here (not in a function) keymap.h:3239: initializer element is not constant keymap.h:3239: (near initialization for `keymapInfos[23].map') *** Error code 1 Stop in /usr/src/usr.sbin/sysinstall. *** Error code 1 cvsupped -CURRENT, 2001-01-25:1811 trying to update an old -CURRENT-2506 source tree. Any ideas? -- Farid Hajji -- Unix Systems and Network Admin | Phone: +49-2131-67-555 Broicherdorfstr. 83, D-41564 Kaarst, Germany | [EMAIL PROTECTED] - - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - Murphy's Law fails only when you try to demonstrate it, and thus succeeds. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [loader?] secret to setting root elsewhere?.
> > If you mean "it loads the kernel from the wrong place", that's one thing. > > If you mean "it mounts / from the wrong filesystem", then you should be > > aware that the loader reads /etc/fstab, and the kernel will mount > > whatever you've put in there. > > > Just curious, but isn't there a checken-and-egg problem here? > > If there is two complete systems, on each disk. If the root on disc 0 > contains an /etc/fstab showing root to be mounted from disk 0, and the root > on disk 1 contains an /etc/fstab showing root to be mounted from disk 1? > > How is it then possible to mount the root on disk 1? By loading a kernel from disk 1, or subsequent to loading the kernel, change $rootdev to point somewhere else. Please don't assume I'm *entirely* stupid. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [loader?] secret to setting root elsewhere?.
> > > #autoboot_delay="10"# Delay in seconds before autobooting
> > > #console="vidconsole" # Set the current console
> > > currdev="disk1s1a" # Set the current device
> > > module_path="/boot/kernel;/boot/modules"# Set the module search path
> > > #prompt="\\${interpret}"# Set the command prompt
> > > root_disk_unit="1" # Force the root disk unit number
> > > rootdev="disk1s1a" # Set the root filesystem
> > >
> > >
> > > but it still loads disk0 as root..
> > >
> > > what am I doing wrong?
> >
> > You don't "load a disk as root".
> >
> > If you mean "it loads the kernel from the wrong place", that's one thing.
> > If you mean "it mounts / from the wrong filesystem", then you should be
> > aware that the loader reads /etc/fstab, and the kernel will mount
> > whatever you've put in there.
>
> YUUU
>
> I'm specifying a different place because the place where fstab is is SCREWED
Ah, shut yer trap. It reads /etc/fstab from wherever the kernel is
loaded from, and if /etc/fstab is hosed/can't be parsed, it'll fall back
to trying to guess using the old algorithms. The new behaviour is a
functional superset of the old.
> but it will let me do what I want.
Of course, you don't actually bother to mention what your problem is, so
I still can't actually *help* you.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
V I C T O R Y N O T V E N G E A N C E
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: > 4GB with NFS?
> VLF-incapable utilities. (on a related note, is there a need for > vlfread()/vlfwrite() in the BSD's, or is VLF support native in the read/write > calls? The standard off_t is 64 bits in all of the BSDs. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: TI-RPC, IPv6 and NFS (was: Re: strong recommendation re: NFS)
Hi, I'll place a new version tomorrow on the server. be patient untill then. Martin Martin Blapp, [EMAIL PROTECTED] Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 On Fri, 26 Jan 2001, Jun Kuriyama wrote: > At 25 Jan 2001 19:08:14 GMT, > Martin Blapp wrote: > > http://www.attic.ch/rpc.diff_01114001.tgz > > I cannot fetch it. Gone into attic? :-) > > > -- > Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc. > <[EMAIL PROTECTED]> // FreeBSD Project > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: TI-RPC, IPv6 and NFS (was: Re: strong recommendation re: NFS)
At 25 Jan 2001 19:08:14 GMT, Martin Blapp wrote: > http://www.attic.ch/rpc.diff_01114001.tgz I cannot fetch it. Gone into attic? :-) -- Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc. <[EMAIL PROTECTED]> // FreeBSD Project To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
buildworld failed and PERL_THREADED=true dead...
Hello. I tried make buildworld after cvsuped my source and it failed in perl area. I remove PERL_THREADED=true and tried again and it failed. ===> usr.bin/kdump cc -O -pipe -march=pentium -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/kdump/kdump.c cc -O -pipe -march=pentium -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/kdump/../ktrace/subr.c gzip -cn /usr/src/usr.bin/kdump/kdump.1 > kdump.1.gz cc -O -pipe -march=pentium -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c ioctl.c In file included from ioctl.c:99: /usr/obj/usr/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined /usr/obj/usr/src/i386/usr/include/pccard/cardinfo.h:81: warning: this is the location of the previous definition In file included from ioctl.c:51: /usr/obj/usr/src/i386/usr/include/machine/i4b_rbch_ioctl.h:45: `TELNO_MAX' undeclared here (not in a function) ioctl.c: In function `ioctlname': ioctl.c:693: invalid use of `restrict' ioctl.c:693: sizeof applied to an incomplete type *** Error code 1 1 error *** Error code 2 FreeBSD 5.0-CURRENT #0: Sat Jan 13 22:57:43 MSK 2001 Any idea? -- Rgdz,/"\ Sergey Osokin aka oZZ, \ / ASCII RIBBON CAMPAIGN [EMAIL PROTECTED]X AGAINST HTML MAIL http://freebsd.org.ru/~osa/ / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [loader?] secret to setting root elsewhere?.
> If you mean "it loads the kernel from the wrong place", that's one thing. > If you mean "it mounts / from the wrong filesystem", then you should be > aware that the loader reads /etc/fstab, and the kernel will mount > whatever you've put in there. > Just curious, but isn't there a checken-and-egg problem here? If there is two complete systems, on each disk. If the root on disc 0 contains an /etc/fstab showing root to be mounted from disk 0, and the root on disk 1 contains an /etc/fstab showing root to be mounted from disk 1? How is it then possible to mount the root on disk 1? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [loader?] secret to setting root elsewhere?.
Mike Smith wrote:
>
> > Ok so I have tried the settings in
> > teh loader conf..
> > I have:
> >
> > #autoboot_delay="10"# Delay in seconds before autobooting
> > #console="vidconsole" # Set the current console
> > currdev="disk1s1a" # Set the current device
> > module_path="/boot/kernel;/boot/modules"# Set the module search path
> > #prompt="\\${interpret}"# Set the command prompt
> > root_disk_unit="1" # Force the root disk unit number
> > rootdev="disk1s1a" # Set the root filesystem
> >
> >
> > but it still loads disk0 as root..
> >
> > what am I doing wrong?
>
> You don't "load a disk as root".
>
> If you mean "it loads the kernel from the wrong place", that's one thing.
> If you mean "it mounts / from the wrong filesystem", then you should be
> aware that the loader reads /etc/fstab, and the kernel will mount
> whatever you've put in there.
YUUU
I'm specifying a different place because the place where fstab is is SCREWED
but it will let me do what I want.
>
> root_disk_unit is also deprecated.
>
> --
> ... every activity meets with opposition, everyone who acts has his
> rivals and unfortunately opponents also. But not because people want
> to be opponents, rather because the tasks and relationships force
> people to take different points of view. [Dr. Fritz Todt]
>V I C T O R Y N O T V E N G E A N C E
--
__--_|\ Julian Elischer
/ \ [EMAIL PROTECTED]
( OZ) World tour 2000
---> X_.---._/ from Perth, presently in: Budapest
v
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: status of bridge code
"Rogier R. Mulhuijzen" wrote:
>
> > > What I want to know is can I just link tap0.upper to a new bridge hook? It
> > > seems to me that is the case.
> >
> >yes I believe so..
> >you can hook as many interfaces as you want to the bridge node.
> >(but you probably don't want to BRIDGE to your cable modem, but to ROUTE
> >to it )
>
> Don't worry =)
>
> I do want to bridge to the tunnel that goes over my cable modem though.
> Make a real VPN there. (And yeah encrypted links)
>
> > > I don't see how though. Lets say I link only to left, right and left2right.
> > > Now when data enters left it will go to both right and left2right. When
> > > data enters right it goes to left. But when data enters left2right it goes
> > > to right, not left, where I want it.
> >
> >no, data entering left2right goes to left.
> >(e. At least it did when I wrote it.. if not let me know )
>
> From ng_tee(4)
>
> Packets may also be received on right2left and left2right; if so, they
> are forwarded unchanged out hooks left and right, respectively.
>
> packets on left2right are delivered on right
>
> And to be sure I checked ng_tee.c:
>
> } else if (hinfo == &sc->left2right) {
> dup = NULL;
> dest = &sc->right;
> }
>
> I'll just add the algorithm to ng_tee...
then I screwed it..
packets from left should go to left2right and packates from left2right should
go
backk to left..
But we haven't ever used that so it may be in error.
>
> DocWilco
--
__--_|\ Julian Elischer
/ \ [EMAIL PROTECTED]
( OZ) World tour 2000
---> X_.---._/ from Perth, presently in: Budapest
v
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: status of bridge code
> > What I want to know is can I just link tap0.upper to a new bridge hook? It
> > seems to me that is the case.
>
>yes I believe so..
>you can hook as many interfaces as you want to the bridge node.
>(but you probably don't want to BRIDGE to your cable modem, but to ROUTE
>to it )
Don't worry =)
I do want to bridge to the tunnel that goes over my cable modem though.
Make a real VPN there. (And yeah encrypted links)
> > I don't see how though. Lets say I link only to left, right and left2right.
> > Now when data enters left it will go to both right and left2right. When
> > data enters right it goes to left. But when data enters left2right it goes
> > to right, not left, where I want it.
>
>no, data entering left2right goes to left.
>(e. At least it did when I wrote it.. if not let me know )
From ng_tee(4)
Packets may also be received on right2left and left2right; if so, they
are forwarded unchanged out hooks left and right, respectively.
packets on left2right are delivered on right
And to be sure I checked ng_tee.c:
} else if (hinfo == &sc->left2right) {
dup = NULL;
dest = &sc->right;
}
I'll just add the algorithm to ng_tee...
DocWilco
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: > 4GB with NFS?
> knowing NFS in general far better than *BSD in specific, I would guess the best > thing to do (if you suspect server/client communication anomaly) is to grab a > snoop/tcpdump of the failure. I'm trying to think of a clever way to cause the > failure immediately, so you're not tracing 4GB of writes... mebbe dd's > seek/skip? or just append to the existing 4GB file. > > also, what command are you using on the bsd's to write the 4GB file? I've lmdd or dd... > definitely seen issues with VLF-capable OS's failing to write past 2/4GB due to > VLF-incapable utilities. (on a related note, is there a need for > vlfread()/vlfwrite() in the BSD's, or is VLF support native in the read/write > calls? An update on this If the server is Solaris, neither NetBSD nor FreeBSD (i386 or alpha) have a problem (as clients). The problem is therefore in some interaction between this server (see http://www.traakan.com- sorta like a NetApp) and *BSD. Hmm!!! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: status of bridge code
"Rogier R. Mulhuijzen" wrote: > > At 09:37 25-1-01 -0800, Archie Cobbs wrote: > >Rogier R. Mulhuijzen writes: > > > But from my list of wishes I'd say the first 3 are gone. All that's > > left is > > > spanning tree. I'm probably going to need this pretty soon, so once more > > > I'm asking if anyone is working on it. If not I'll start on it. > > > >Do you have references for how to do this? As I understand it, there > >are special Ethernet addresses that are "for bridges only -- do not > >forward" that are used to construct the spanning tree, etc. What is > >the "standard" algorithm used by bridges, etc.? > > There's a Spanning Tree Protocol (STP) defined by IEEE 802.1D. I'd prefer > to have that, but I don't have the 1K US$ to shell out for that. > Does BSDi have IEEE subscriptions for FreeBSD developers to use? > > Anyway, even without the IEEE standard I have been able to piece together > how the protocol works. > > First of all bridges might have their own MACs that fall into a certain > range, but STP does not depend on that. The "do not forward" is deducted > from the protocol type. There is an ethernet protocol called BPDU (Bridge > Protocol Data Unit) that each bridge sends and receives, but is not > forwarded by any of them. These BDPUs are used to elect root bridge and > determine root ports and designated ports. > > This results in the blocking of redundant ports so that loops are > eliminated. See http://www.knowcisco.com/content/1578700949/pt02ch06.shtml > for a good overview that's pretty in depth. > > About those blocked ports though I have a question. I've been reading > ng_bridge.c and blocking a link in there (a tad more finegrained than right > now) should not be a problem. But it seems to me that with the bridge.ether > example there might be a problem. I'm using my own situation at home as an > example to sketch this out. Please correct me if I'm wrong. > > 1 real NIC connected to LAN with ed0 as interface > 1 tap device ran by vtun with tap0 as interface > 1 tun device connected to cablemodem with tun0 as interface > > I have a netgraph bridge node that has ed0 and tap0 as interfaces, and ed0 > as local interface (as per the example script) > > This means that packets from kernel to LAN go through the bridge node > (thanks to the link from ed0.upper to the bridge) but packets from the > kernel to the tap0 interface don't go through it (no link from tap0.upper > to bridge). This means the bridge node has no idea where the MAC of the > tap0 device is located (not stored in the MAC table of the bridge). So when > packets directed at my tap0 interface enter the bridge (through the link > from tap0.lower to the bridge) the bridge doesn't have a clue where to send > it, and will thus forward to all links. Thus it will go through ed0.upper > and end up in the kernel, no harm done. BUT it will also go out ed0.lower > and end up in my LAN where it doesn't belong. > > Right now I don't mind because the traffic my cablemodem can handle is > 8KB/s max. But it is not desired behaviour of a bridge. > > What I want to know is can I just link tap0.upper to a new bridge hook? It > seems to me that is the case. yes I believe so.. you can hook as many interfaces as you want to the bridge node. (but you probably don't want to BRIDGE to your cable modem, but to ROUTE to it ) > > If that's true the example script should be altered because right now it > doesn't support more than one interface. Just say the word and I'll take > care of it. =) > > > > Also, a quick question for you netgraph guys. Why is it that ng_one2many > > > send a packet only out of one hook? I can see use for an algorithm that > > > sends packets from the 'one' hook to all the 'many' hooks (that are up) > > and > > > keep the normal behaviour for many to one. > > > >Hmm.. you could also get that affect using log2(n) ng_tee(4) nodes.. > > I don't see how though. Lets say I link only to left, right and left2right. > Now when data enters left it will go to both right and left2right. When > data enters right it goes to left. But when data enters left2right it goes > to right, not left, where I want it. no, data entering left2right goes to left. (e. At least it did when I wrote it.. if not let me know ) > > DocWilco -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000 ---> X_.---._/ from Perth, presently in: Budapest v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: status of bridge code
Rogier R. Mulhuijzen writes: > >Hmm.. you could also get that affect using log2(n) ng_tee(4) nodes.. > > I don't see how though. Lets say I link only to left, right and left2right. > Now when data enters left it will go to both right and left2right. When > data enters right it goes to left. But when data enters left2right it goes > to right, not left, where I want it. Think of each tee node as a 2x packet doubler, then hook them up like this: --- o --- \ o-- \ o \ o-- \ o \ o-- \ o I.e., only use "left", "right", and "left2right". -Archie __ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: > 4GB with NFS?
* Nathan Parrish <[EMAIL PROTECTED]> [010125 13:19] wrote: > knowing NFS in general far better than *BSD in specific, I would guess the best > thing to do (if you suspect server/client communication anomaly) is to grab a > snoop/tcpdump of the failure. I'm trying to think of a clever way to cause the > failure immediately, so you're not tracing 4GB of writes... mebbe dd's > seek/skip? or just append to the existing 4GB file. > > also, what command are you using on the bsd's to write the 4GB file? I've > definitely seen issues with VLF-capable OS's failing to write past 2/4GB due to > VLF-incapable utilities. (on a related note, is there a need for > vlfread()/vlfwrite() in the BSD's, or is VLF support native in the read/write > calls? It has to do with the vm system casting values into 32bit variables, it's been a long time since I looked at this, if I can find it again I might be able to do something about it. To answer your question about VLF (which I had to guess at) assuming you mean Very Large Files: 1) yes some tools break on them, I don't have a list handy. 2) BSD has had native VLF support since 4.4-BSD. (off_t is 64bit) -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: > 4GB with NFS?
knowing NFS in general far better than *BSD in specific, I would guess the best thing to do (if you suspect server/client communication anomaly) is to grab a snoop/tcpdump of the failure. I'm trying to think of a clever way to cause the failure immediately, so you're not tracing 4GB of writes... mebbe dd's seek/skip? or just append to the existing 4GB file. also, what command are you using on the bsd's to write the 4GB file? I've definitely seen issues with VLF-capable OS's failing to write past 2/4GB due to VLF-incapable utilities. (on a related note, is there a need for vlfread()/vlfwrite() in the BSD's, or is VLF support native in the read/write calls? nathan --- Matthew Jacob <[EMAIL PROTECTED]> wrote: > > To be fair, I should say that the server is a 'specical' box. > > But an lmdd writing to a file in 250GB partition that I started from Solaris > last night is still going. The NetBSD && FreeBSD writes both stopped at 4GB. > I > suppose it still could be the server, but, well, it's hard to sell against > something that "just works"... .:-) > > > On Thu, 25 Jan 2001, Matthew Jacob wrote: > > > > > On Thu, 25 Jan 2001, Dan Nelson wrote: > > > > > In the last episode (Jan 25), Matthew Jacob said: > > > > I came across an embarrassing comparison last night- > > > > > > > > FreeBSD NFS clients (well, i386) stop writing files at 4GB. > > > > > > > > Solaris, with O_LARGEFILE options in the open arguments, does not. > > > > > > > > Does anyone here know what FreeBSD ought to be doing about this? Or > > > > have I missed something? There is no O_LARGEFILE in fcntl.h (it is > > > > present for Solaris, ConvexOS and some other platforms, I believe). I > > > > thought the *BSDs had > 32 bit file support? Or is it only for local > > > > filesystems? > > > > > > FreeBSD has 64-bit file offsets by default, which make -DLARGEFILE > > > hackery unnecessary. > > > > So I thought! > > > > > > > > Make sure you're using NFSv3 mounts (should be the default, but if not, > > > add "nfsv3" to the options column in fstab). I cross-mount FreeBSD, > > > Tru64, and Solaris boxes via NFS and can access large files on all > > > combinations of client and server. > > > > Huh. Interesting. The default showed up as a nfsv3 mount: > > > > 1/25 2:12 mountd/v3: granted 192.67.166.79 to /bob ro=0 uid0=60001 > > > > The solaris mount showed up as: > > > > 1/25 2:06 mountd/v3: granted 192.67.166.155 to /bob ro=0 uid0=60001 > > 1/25 2:06 nfs/tcp accepted 192.67.166.155,1023 > > > > I'll try an explicit v3 mount/tcp and see if it's better. > > > > > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-current" in the body of the message > > > __ Do You Yahoo!? Yahoo! Auctions - Buy the things you want at great prices. http://auctions.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [loader?] secret to setting root elsewhere?.
> Ok so I have tried the settings in
> teh loader conf..
> I have:
>
> #autoboot_delay="10"# Delay in seconds before autobooting
> #console="vidconsole" # Set the current console
> currdev="disk1s1a" # Set the current device
> module_path="/boot/kernel;/boot/modules"# Set the module search path
> #prompt="\\${interpret}"# Set the command prompt
> root_disk_unit="1" # Force the root disk unit number
> rootdev="disk1s1a" # Set the root filesystem
>
>
> but it still loads disk0 as root..
>
> what am I doing wrong?
You don't "load a disk as root".
If you mean "it loads the kernel from the wrong place", that's one thing.
If you mean "it mounts / from the wrong filesystem", then you should be
aware that the loader reads /etc/fstab, and the kernel will mount
whatever you've put in there.
root_disk_unit is also deprecated.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
V I C T O R Y N O T V E N G E A N C E
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: status of bridge code
At 09:37 25-1-01 -0800, Archie Cobbs wrote: >Rogier R. Mulhuijzen writes: > > But from my list of wishes I'd say the first 3 are gone. All that's > left is > > spanning tree. I'm probably going to need this pretty soon, so once more > > I'm asking if anyone is working on it. If not I'll start on it. > >Do you have references for how to do this? As I understand it, there >are special Ethernet addresses that are "for bridges only -- do not >forward" that are used to construct the spanning tree, etc. What is >the "standard" algorithm used by bridges, etc.? There's a Spanning Tree Protocol (STP) defined by IEEE 802.1D. I'd prefer to have that, but I don't have the 1K US$ to shell out for that. Does BSDi have IEEE subscriptions for FreeBSD developers to use? Anyway, even without the IEEE standard I have been able to piece together how the protocol works. First of all bridges might have their own MACs that fall into a certain range, but STP does not depend on that. The "do not forward" is deducted from the protocol type. There is an ethernet protocol called BPDU (Bridge Protocol Data Unit) that each bridge sends and receives, but is not forwarded by any of them. These BDPUs are used to elect root bridge and determine root ports and designated ports. This results in the blocking of redundant ports so that loops are eliminated. See http://www.knowcisco.com/content/1578700949/pt02ch06.shtml for a good overview that's pretty in depth. About those blocked ports though I have a question. I've been reading ng_bridge.c and blocking a link in there (a tad more finegrained than right now) should not be a problem. But it seems to me that with the bridge.ether example there might be a problem. I'm using my own situation at home as an example to sketch this out. Please correct me if I'm wrong. 1 real NIC connected to LAN with ed0 as interface 1 tap device ran by vtun with tap0 as interface 1 tun device connected to cablemodem with tun0 as interface I have a netgraph bridge node that has ed0 and tap0 as interfaces, and ed0 as local interface (as per the example script) This means that packets from kernel to LAN go through the bridge node (thanks to the link from ed0.upper to the bridge) but packets from the kernel to the tap0 interface don't go through it (no link from tap0.upper to bridge). This means the bridge node has no idea where the MAC of the tap0 device is located (not stored in the MAC table of the bridge). So when packets directed at my tap0 interface enter the bridge (through the link from tap0.lower to the bridge) the bridge doesn't have a clue where to send it, and will thus forward to all links. Thus it will go through ed0.upper and end up in the kernel, no harm done. BUT it will also go out ed0.lower and end up in my LAN where it doesn't belong. Right now I don't mind because the traffic my cablemodem can handle is 8KB/s max. But it is not desired behaviour of a bridge. What I want to know is can I just link tap0.upper to a new bridge hook? It seems to me that is the case. If that's true the example script should be altered because right now it doesn't support more than one interface. Just say the word and I'll take care of it. =) > > Also, a quick question for you netgraph guys. Why is it that ng_one2many > > send a packet only out of one hook? I can see use for an algorithm that > > sends packets from the 'one' hook to all the 'many' hooks (that are up) > and > > keep the normal behaviour for many to one. > >Hmm.. you could also get that affect using log2(n) ng_tee(4) nodes.. I don't see how though. Lets say I link only to left, right and left2right. Now when data enters left it will go to both right and left2right. When data enters right it goes to left. But when data enters left2right it goes to right, not left, where I want it. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: status of bridge code
>this would be a REALLY easy node to write...maybe your first? >(see how 'ng_tee' works and ng_one2many, and >write one that does something in between. I was thinking adding an algorithm to one2many. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[loader?] secret to setting root elsewhere?.
Ok so I have tried the settings in
teh loader conf..
I have:
#autoboot_delay="10"# Delay in seconds before autobooting
#console="vidconsole" # Set the current console
currdev="disk1s1a" # Set the current device
module_path="/boot/kernel;/boot/modules"# Set the module search path
#prompt="\\${interpret}"# Set the command prompt
root_disk_unit="1" # Force the root disk unit number
rootdev="disk1s1a" # Set the root filesystem
but it still loads disk0 as root..
what am I doing wrong?
(this is the conf file on the 2nd disk..)
I hit F5 (2nd disk)
then F1 (FreeBSD)
and then it loads the loader.
I examined the settings and they appear right in the loader.
(It uses the 2nd disk while loading the kernel so Iassume that
it is correct)
but is still mounts ad0s4a as root
what am I doing wrong..?
--
__--_|\ Julian Elischer
/ \ [EMAIL PROTECTED]
( OZ) World tour 2000
---> X_.---._/ from Perth, presently in: Budapest
v
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: TI-RPC, IPv6 and NFS (was: Re: strong recommendation re: NFS)
* Martin Blapp <[EMAIL PROTECTED]> [010125 11:07] wrote: > > Hi, > > Alfred Perlstein and I have ported TI-RPC to FreeBSD Current. You can find > the latest snapshot here: > > http://www.attic.ch/rpc.diff_01114001.tgz > > Patches and bugfixes are welcome. Can you post a summary of how you've done it and what you've done to it since we last worked on this? Nothing big, just a few points on what it gives us and what you've done (or not done) about the TLI junk that it's encumbered with. thanks, -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: status of bridge code
Archie Cobbs wrote: > > Rogier R. Mulhuijzen writes: > > > Also, a quick question for you netgraph guys. Why is it that ng_one2many > > send a packet only out of one hook? I can see use for an algorithm that > > sends packets from the 'one' hook to all the 'many' hooks (that are up) and > > keep the normal behaviour for many to one. this would be a REALLY easy node to write...maybe your first? (see how 'ng_tee' works and ng_one2many, and write one that does something in between. -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000 ---> X_.---._/ from Perth, presently in: Budapest v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bootstrapping issues with groff(1)
[I don't know why -current is CC'd this is clearly about -stable] Ruslan Ermilov wrote: > > Attached is the patch for RELENG_4. It works but I don't like > how it pollutes the Makefile.inc1. Anyone with a better idea? Allow me to sidetrack for a moment: I just ugraded a machine from 4.1 to 4.2-stable without any problems. I'm a bit confused. Rene picks up RELENG_4 and sees his build fail. Why did it work for me? -- Marcel Moolenaar mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] tel: (408) 447-4222 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
TI-RPC, IPv6 and NFS (was: Re: strong recommendation re: NFS)
Hi, Alfred Perlstein and I have ported TI-RPC to FreeBSD Current. You can find the latest snapshot here: http://www.attic.ch/rpc.diff_01114001.tgz Patches and bugfixes are welcome. Martin Martin Blapp, [EMAIL PROTECTED] Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: > 4GB with NFS?
> > Matthew Jacob writes: > > > > Same code compiled on Solaris is happy. > > Perhaps there's some braindamage in it. I'm afraid of something like: > > #ifdef Solaris > typedef filefoo u_int64_t; > #else > typedef filefoo u_int32_t; > #endif > I'll try with dd then,... let y'all know... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: > 4GB with NFS?
Matthew Jacob writes: > > Same code compiled on Solaris is happy. Perhaps there's some braindamage in it. I'm afraid of something like: #ifdef Solaris typedef filefoo u_int64_t; #else typedef filefoo u_int32_t; #endif ;) Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: status of bridge code
"Rogier R. Mulhuijzen" wrote: > > >personally I use the netgraph bridging code and I think (though I'm biased) > >that you should look at using htat rather than the hardwired bridging > >code that it was derived from. > > Now that I've read up on it I can tell you you and and Archie have every > right to be biased =) > > I've had a netgraph bridge in place for a while now and it works very well. > (On 4.X-STABLE, on 5.X-CURRENT it went kablooie. See panic trace) where is it? (have you tried it REALLY recently?) > > > > item on my list. Being an allround good networking OS this is unacceptable > > > IMHO. > > > >Have a look at what you can do with netgraph first. > > > >Most people don't know what it is but it allows almost arbitrarily > >complicated network topologies to be set up from the command line. > > What you might want to tell people is that it allows networking structures > to be setup in a simple manner, but is so powerful it can also be used for > immensely complex structures. A friend and fellow BSD user of mine's first > response was "I like to keep things simple". After I rephrased into the > above he was much more interested. > > But from my list of wishes I'd say the first 3 are gone. All that's left is > spanning tree. I'm probably going to need this pretty soon, so once more > I'm asking if anyone is working on it. If not I'll start on it. > > Also, a quick question for you netgraph guys. Why is it that ng_one2many > send a packet only out of one hook? I can see use for an algorithm that > sends packets from the 'one' hook to all the 'many' hooks (that are up) and > keep the normal behaviour for many to one. > > DocWilco -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000 ---> X_.---._/ from Perth, presently in: Budapest v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: > 4GB with NFS?
On Thu, 25 Jan 2001, Andrew Gallatin wrote: > > Matthew Jacob writes: > > > > I came across an embarrassing comparison last night- > > > > FreeBSD NFS clients (well, i386) stop writing files at 4GB. > > > > Solaris, with O_LARGEFILE options in the open arguments, does not. > > > > Does anyone here know what FreeBSD ought to be doing about this? > > Or have I missed something? There is no O_LARGEFILE in fcntl.h (it is present > > for Solaris, ConvexOS and some other platforms, I believe). I thought the > > *BSDs had > 32 bit file support? Or is it only for local filesystems? > > > > -matt > > Normal /bin/dd works fine between on 4.2-RELEASE i386s here. > > This is writing to a raid0 fs on a FreeBSD/i386 server using an nfsv3 > mount, udp, 8k read/write size: > > % dd if=/dev/zero of=bigfile bs=1024k count=5000 > 5000+0 records in > 5000+0 records out > 524288 bytes transferred in 471.673794 secs (5479 bytes/sec) > > This is writing to a software raid5 fs on a Solaris/x86 (2.8) server > using an nfsv3 mount, udp, 8k read/write size: > > % dd if=/dev/zero of=bigfile bs=1024k count=5000 > 5000+0 records in > 5000+0 records out > 524288 bytes transferred in 1165.859965 secs (4497007 bytes/sec) > > Maybe you should look at "lmdd" ? Maybe it is either buggy, or it was > compiled a long, long time ago? Same code compiled on Solaris is happy. > (btw, this is a virgin 4.2 install, with none of my nfs opts in it). Hmm. Well, everyone sez this oughta work so I'll go and figure out why it ain't for me... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: > 4GB with NFS?
Matthew Jacob writes: > > I came across an embarrassing comparison last night- > > FreeBSD NFS clients (well, i386) stop writing files at 4GB. > > Solaris, with O_LARGEFILE options in the open arguments, does not. > > Does anyone here know what FreeBSD ought to be doing about this? > Or have I missed something? There is no O_LARGEFILE in fcntl.h (it is present > for Solaris, ConvexOS and some other platforms, I believe). I thought the > *BSDs had > 32 bit file support? Or is it only for local filesystems? > > -matt Normal /bin/dd works fine between on 4.2-RELEASE i386s here. This is writing to a raid0 fs on a FreeBSD/i386 server using an nfsv3 mount, udp, 8k read/write size: % dd if=/dev/zero of=bigfile bs=1024k count=5000 5000+0 records in 5000+0 records out 524288 bytes transferred in 471.673794 secs (5479 bytes/sec) This is writing to a software raid5 fs on a Solaris/x86 (2.8) server using an nfsv3 mount, udp, 8k read/write size: % dd if=/dev/zero of=bigfile bs=1024k count=5000 5000+0 records in 5000+0 records out 524288 bytes transferred in 1165.859965 secs (4497007 bytes/sec) Maybe you should look at "lmdd" ? Maybe it is either buggy, or it was compiled a long, long time ago? (btw, this is a virgin 4.2 install, with none of my nfs opts in it). Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: status of bridge code
Hi, > > But from my list of wishes I'd say the first 3 are gone. All that's left is > > spanning tree. I'm probably going to need this pretty soon, so once more > > I'm asking if anyone is working on it. If not I'll start on it. > > Do you have references for how to do this? As I understand it, there > are special Ethernet addresses that are "for bridges only -- do not > forward" that are used to construct the spanning tree, etc. What is > the "standard" algorithm used by bridges, etc.? After a quick search on google for "spanning tree" and "BPDU", here are some usefull links: http://www.ece.wpi.edu/courses/ee535/hwk96/hwk3cd96/sef/sef.html http://www.synapse.de/ban/HTML/P_LAYER2/Eng/P_lay119.html http://www.ethereal.com/lists/ethereal-dev/199910/msg00070.html http://www.support.baynetworks.com/library/tpubs/html/router/soft1000/bridge /2950A-16.html Apparently there is an implementation in linux (look for the file net/bridge/br_stp_bpdu.c) and the "BRIDGE-STP-HOWTO" (http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/BRIDG E-STP-HOWTO.html) http://www.linuxhq.com/kernel/v2.3/patch/patch-2.3.47/linux_net_bridge_br_st p.c.html Patrick. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic in netgraph (caught by WITNESS) in custom UP kernel
"Rogier R. Mulhuijzen" wrote: > > FYI: > > Full source CVSupped on the 18th or 19th > > Panic came about when I did a 'ls' in ngctl(8). > > Kernel config attached, gdb of core follows below: > > This GDB was configured as "i386-unknown-freebsd"... > IdlePTD 5300224 > initial pcb at 31c4e0 > panicstr: from debugger > panic messages: > --- > panic: mutex_enter: MTX_SPIN on MTX_DEF mutex netgraph node mutex @ > ../../netgraph/ng_base.c:2205 > panic: from debugger > Uptime: 1d4h5m24s I think I fixed this yesterday by adding MTX_SPIN to the mtx_init() call. let me know if that isn't the case (check you have the last patch to ng_base.c) -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000 ---> X_.---._/ from Perth, presently in: Budapest v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: > 4GB with NFS?
> > But I won't let it go! I was hoping to replace my Solaris box with either > > FreeBSD or NetBSD as my main home directory server. FreeBSD 4.2 panics part > > way through the first LADDIS runs I was using to test it with and I can't get > > NetBSD to start as a LADDIS client (I hadn't got the auth sorted out yet), so > > I've been trying to scrutinize a lot of things very closely in this area. > > This is an old problem that I think was never addressed. It has to > do with the vm system (on i386). It may be fixed now, so keep playing > a bit, if not open a problem report and someone ought to get to it. Yah, I was gonna do that once -current stabilized a bit. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bw limit in netgraph (Was: status of bridge code)
Rogier R. Mulhuijzen writes: > Quick question for the netgraph guru's. I haven't looked yet, but is there > an explanation of the NG_ macros I see used in the netgraph nodes' code? Yes, but it's not documented :) Actually the daemonnews article does document these somewhat. The main ones are NG_MKMESSAGE() for creating a new control message and NG_MKRESPONSE() for creating a response to a control message; and NG_SEND_DATA() to send a data/meta pair, NG_FREE_DATA() to free one. -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: status of bridge code
Rogier R. Mulhuijzen writes: > But from my list of wishes I'd say the first 3 are gone. All that's left is > spanning tree. I'm probably going to need this pretty soon, so once more > I'm asking if anyone is working on it. If not I'll start on it. Do you have references for how to do this? As I understand it, there are special Ethernet addresses that are "for bridges only -- do not forward" that are used to construct the spanning tree, etc. What is the "standard" algorithm used by bridges, etc.? > Also, a quick question for you netgraph guys. Why is it that ng_one2many > send a packet only out of one hook? I can see use for an algorithm that > sends packets from the 'one' hook to all the 'many' hooks (that are up) and > keep the normal behaviour for many to one. Hmm.. you could also get that affect using log2(n) ng_tee(4) nodes.. -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: > 4GB with NFS?
* Matthew Jacob <[EMAIL PROTECTED]> [010125 09:18] wrote: > > > On Thu, 25 Jan 2001, Dan Nelson wrote: > > > In the last episode (Jan 25), Matthew Jacob said: > > > On Thu, 25 Jan 2001, Dan Nelson wrote: > > > > Make sure you're using NFSv3 mounts (should be the default, but if not, > > > > add "nfsv3" to the options column in fstab). I cross-mount FreeBSD, > > > > Tru64, and Solaris boxes via NFS and can access large files on all > > > > combinations of client and server. > > > > > > Huh. Interesting. The default showed up as a nfsv3 mount: > > > > > > 1/25 2:12 mountd/v3: granted 192.67.166.79 to /bob ro=0 uid0=60001 > > > > > > The solaris mount showed up as: > > > > > > 1/25 2:06 mountd/v3: granted 192.67.166.155 to /bob ro=0 uid0=60001 > > > 1/25 2:06 nfs/tcp accepted 192.67.166.155,1023 > > > > > > I'll try an explicit v3 mount/tcp and see if it's better. > > > > I use UDP mounts as it's easier to debug traces. > > > > The next step is to start looking as packet dumps... When you say that > > the FreeBSD clients "stop writing", what error do they get? > > None. As in EOF. > > > Also, what > > version of FreeBSD are you using? > > 4.2 in this case. 1.5.1 for NetBSD. > > > Okay- I think from what you've said and what Thor said for NetBSD is that this > is "supposed to work!" (which accords with what *I* thought too). I'll do some > more debugging as I can (I'm in a project deadline for 3 projects this week). > > But I won't let it go! I was hoping to replace my Solaris box with either > FreeBSD or NetBSD as my main home directory server. FreeBSD 4.2 panics part > way through the first LADDIS runs I was using to test it with and I can't get > NetBSD to start as a LADDIS client (I hadn't got the auth sorted out yet), so > I've been trying to scrutinize a lot of things very closely in this area. This is an old problem that I think was never addressed. It has to do with the vm system (on i386). It may be fixed now, so keep playing a bit, if not open a problem report and someone ought to get to it. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: > 4GB with NFS?
On Thu, 25 Jan 2001, Dan Nelson wrote: > In the last episode (Jan 25), Matthew Jacob said: > > On Thu, 25 Jan 2001, Dan Nelson wrote: > > > Make sure you're using NFSv3 mounts (should be the default, but if not, > > > add "nfsv3" to the options column in fstab). I cross-mount FreeBSD, > > > Tru64, and Solaris boxes via NFS and can access large files on all > > > combinations of client and server. > > > > Huh. Interesting. The default showed up as a nfsv3 mount: > > > > 1/25 2:12 mountd/v3: granted 192.67.166.79 to /bob ro=0 uid0=60001 > > > > The solaris mount showed up as: > > > > 1/25 2:06 mountd/v3: granted 192.67.166.155 to /bob ro=0 uid0=60001 > > 1/25 2:06 nfs/tcp accepted 192.67.166.155,1023 > > > > I'll try an explicit v3 mount/tcp and see if it's better. > > I use UDP mounts as it's easier to debug traces. > > The next step is to start looking as packet dumps... When you say that > the FreeBSD clients "stop writing", what error do they get? None. As in EOF. > Also, what > version of FreeBSD are you using? 4.2 in this case. 1.5.1 for NetBSD. Okay- I think from what you've said and what Thor said for NetBSD is that this is "supposed to work!" (which accords with what *I* thought too). I'll do some more debugging as I can (I'm in a project deadline for 3 projects this week). But I won't let it go! I was hoping to replace my Solaris box with either FreeBSD or NetBSD as my main home directory server. FreeBSD 4.2 panics part way through the first LADDIS runs I was using to test it with and I can't get NetBSD to start as a LADDIS client (I hadn't got the auth sorted out yet), so I've been trying to scrutinize a lot of things very closely in this area. -matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: > 4GB with NFS?
To be fair, I should say that the server is a 'specical' box. But an lmdd writing to a file in 250GB partition that I started from Solaris last night is still going. The NetBSD && FreeBSD writes both stopped at 4GB. I suppose it still could be the server, but, well, it's hard to sell against something that "just works"... .:-) On Thu, 25 Jan 2001, Matthew Jacob wrote: > > On Thu, 25 Jan 2001, Dan Nelson wrote: > > > In the last episode (Jan 25), Matthew Jacob said: > > > I came across an embarrassing comparison last night- > > > > > > FreeBSD NFS clients (well, i386) stop writing files at 4GB. > > > > > > Solaris, with O_LARGEFILE options in the open arguments, does not. > > > > > > Does anyone here know what FreeBSD ought to be doing about this? Or > > > have I missed something? There is no O_LARGEFILE in fcntl.h (it is > > > present for Solaris, ConvexOS and some other platforms, I believe). I > > > thought the *BSDs had > 32 bit file support? Or is it only for local > > > filesystems? > > > > FreeBSD has 64-bit file offsets by default, which make -DLARGEFILE > > hackery unnecessary. > > So I thought! > > > > > Make sure you're using NFSv3 mounts (should be the default, but if not, > > add "nfsv3" to the options column in fstab). I cross-mount FreeBSD, > > Tru64, and Solaris boxes via NFS and can access large files on all > > combinations of client and server. > > Huh. Interesting. The default showed up as a nfsv3 mount: > > 1/25 2:12 mountd/v3: granted 192.67.166.79 to /bob ro=0 uid0=60001 > > The solaris mount showed up as: > > 1/25 2:06 mountd/v3: granted 192.67.166.155 to /bob ro=0 uid0=60001 > 1/25 2:06 nfs/tcp accepted 192.67.166.155,1023 > > I'll try an explicit v3 mount/tcp and see if it's better. > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: > 4GB with NFS?
In the last episode (Jan 25), Matthew Jacob said: > On Thu, 25 Jan 2001, Dan Nelson wrote: > > Make sure you're using NFSv3 mounts (should be the default, but if not, > > add "nfsv3" to the options column in fstab). I cross-mount FreeBSD, > > Tru64, and Solaris boxes via NFS and can access large files on all > > combinations of client and server. > > Huh. Interesting. The default showed up as a nfsv3 mount: > > 1/25 2:12 mountd/v3: granted 192.67.166.79 to /bob ro=0 uid0=60001 > > The solaris mount showed up as: > > 1/25 2:06 mountd/v3: granted 192.67.166.155 to /bob ro=0 uid0=60001 > 1/25 2:06 nfs/tcp accepted 192.67.166.155,1023 > > I'll try an explicit v3 mount/tcp and see if it's better. I use UDP mounts as it's easier to debug traces. The next step is to start looking as packet dumps... When you say that the FreeBSD clients "stop writing", what error do they get? Also, what version of FreeBSD are you using? -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: > 4GB with NFS?
On Thu, 25 Jan 2001, Dan Nelson wrote: > In the last episode (Jan 25), Matthew Jacob said: > > I came across an embarrassing comparison last night- > > > > FreeBSD NFS clients (well, i386) stop writing files at 4GB. > > > > Solaris, with O_LARGEFILE options in the open arguments, does not. > > > > Does anyone here know what FreeBSD ought to be doing about this? Or > > have I missed something? There is no O_LARGEFILE in fcntl.h (it is > > present for Solaris, ConvexOS and some other platforms, I believe). I > > thought the *BSDs had > 32 bit file support? Or is it only for local > > filesystems? > > FreeBSD has 64-bit file offsets by default, which make -DLARGEFILE > hackery unnecessary. So I thought! > > Make sure you're using NFSv3 mounts (should be the default, but if not, > add "nfsv3" to the options column in fstab). I cross-mount FreeBSD, > Tru64, and Solaris boxes via NFS and can access large files on all > combinations of client and server. Huh. Interesting. The default showed up as a nfsv3 mount: 1/25 2:12 mountd/v3: granted 192.67.166.79 to /bob ro=0 uid0=60001 The solaris mount showed up as: 1/25 2:06 mountd/v3: granted 192.67.166.155 to /bob ro=0 uid0=60001 1/25 2:06 nfs/tcp accepted 192.67.166.155,1023 I'll try an explicit v3 mount/tcp and see if it's better. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: > 4GB with NFS?
In the last episode (Jan 25), Matthew Jacob said: > I came across an embarrassing comparison last night- > > FreeBSD NFS clients (well, i386) stop writing files at 4GB. > > Solaris, with O_LARGEFILE options in the open arguments, does not. > > Does anyone here know what FreeBSD ought to be doing about this? Or > have I missed something? There is no O_LARGEFILE in fcntl.h (it is > present for Solaris, ConvexOS and some other platforms, I believe). I > thought the *BSDs had > 32 bit file support? Or is it only for local > filesystems? FreeBSD has 64-bit file offsets by default, which make -DLARGEFILE hackery unnecessary. Make sure you're using NFSv3 mounts (should be the default, but if not, add "nfsv3" to the options column in fstab). I cross-mount FreeBSD, Tru64, and Solaris boxes via NFS and can access large files on all combinations of client and server. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
> 4GB with NFS?
I came across an embarrassing comparison last night- FreeBSD NFS clients (well, i386) stop writing files at 4GB. Solaris, with O_LARGEFILE options in the open arguments, does not. Does anyone here know what FreeBSD ought to be doing about this? Or have I missed something? There is no O_LARGEFILE in fcntl.h (it is present for Solaris, ConvexOS and some other platforms, I believe). I thought the *BSDs had > 32 bit file support? Or is it only for local filesystems? -matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bw limit in netgraph (Was: status of bridge code)
> > Since I currently have high workload, I dont have time to port it to 4.x or > 5-CURRENT... > Conclusion: volunteer required for this work... and I can consult him/her. Shouldn't be too hard. I'll gladly volunteer for this project. Quick question for the netgraph guru's. I haven't looked yet, but is there an explanation of the NG_ macros I see used in the netgraph nodes' code? DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: (KAME-snap 3976) Re: TI-RPC, IPv6 and NFS (was: Re: strong recommendation re: NFS)
>> The above is correct. NetBSD NFS-over-IPv6 (actually RPC over IPv6) >> is TI-RPC based, and it was done by NetBSD guys not KAME guys. >Sorry, I was not clear. The question about moving towards TI-RPC was >directed to freebsd-current. Just out of interest. No critisism intended. no, i did not took it as criticism. i (and feico) just tried to clarify. itojun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: (KAME-snap 3974) Re: TI-RPC, IPv6 and NFS (was: Re: strong recommendation re: NFS)
In your previous mail you wrote: It is not impossible to support IPv6 NFS without switching to TI-RPC, INRIA IPv6 has the code (IIRC). => this code was ported to FreeBSD 4.2. I'll give more details as soon as I am back to my office (ie. next week). However, if you try this, there will be a lot of of non-intuitive typecast against library arguments. => this is a matter of taste. TI-RPC is not perfect tooo (:-). Thanks [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: (KAME-snap 3974) Re: TI-RPC, IPv6 and NFS (was: Re: strongrecommendation re: NFS)
On Thu, 25 Jan 2001 [EMAIL PROTECTED] wrote: > >I don't think this is within the KAME-project scope. On NetBSD, the > >NetBSD crowd has done this almost a year ago (I believe) and NFS over > >IPv6 works just great on NetBSD. I'd guess FreeBSD could borrow a lot > >from the NetBSD work, reducing the major-ness of the task? > > The above is correct. NetBSD NFS-over-IPv6 (actually RPC over IPv6) > is TI-RPC based, and it was done by NetBSD guys not KAME guys. Sorry, I was not clear. The question about moving towards TI-RPC was directed to freebsd-current. Just out of interest. No critisism intended. rvdp To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: (KAME-snap 3972) TI-RPC, IPv6 and NFS (was: Re: strong recommendation re: NFS)
>I don't think this is within the KAME-project scope. On NetBSD, the >NetBSD crowd has done this almost a year ago (I believe) and NFS over >IPv6 works just great on NetBSD. I'd guess FreeBSD could borrow a lot >from the NetBSD work, reducing the major-ness of the task? The above is correct. NetBSD NFS-over-IPv6 (actually RPC over IPv6) is TI-RPC based, and it was done by NetBSD guys not KAME guys. It is not impossible to support IPv6 NFS without switching to TI-RPC, INRIA IPv6 has the code (IIRC). However, if you try this, there will be a lot of of non-intuitive typecast against library arguments. itojun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
parallel port zip+ fix
Hi all, I have been working with Nicholas Souchu to fix a few issues with the parallel port zip, especially the zip+ (250 meg version). I know this is deprecated hardware, but I would like to know if it helps. The driver should now work correctly in PS2 transfer mode, which in theory should be twice as fast as NIBBLE mode. Set the flags for ppc to 0x00, so the driver will detect all available modes and choose the best one. Probing and mode selection has been much improved, thanks to Nicholas' work. If you want to force PS2 mode, that should work as well. Please let me know if you have any problems. jcm -- o-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-o | Jonathon McKitrick ~ | | "I prefer the term 'Artificial Person' myself." | o-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-o To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: libc/libc_r changes require rebuild of threaded apps
On Wed, 24 Jan 2001, Maxim Sobolev wrote: > > It's not a very accurate estimate, as the magic can be in the distfile > itself, i.e. properly written configure script or makefile may know > that FreeBSD need a -pthread and -D_THREAD_SAFE. > For some unknown reason, math.h needs _REENTRANT in FreeBSD to declare gamma_r, lgamma_r, gammaf_r and lgammaf_r. Perhaps this could be changed too. I don't know what the POSIX standard says about this. -- Carlos A. M. dos Santos Federal University of Pelotas Meteorological Research Center Av. Ildefonso Simoes Lopes 2791 Pelotas, RS, Brasil, CEP 96060-290 WWW: http://www.cpmet.ufpel.tche.br RENPAC (X.25): 153231641 Phone: +55 53 277-6767FAX: +55 53 277-6722 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: (KAME-snap 3972) TI-RPC, IPv6 and NFS (was: Re: strong recommendation re: NFS)
On Thu, Jan 25, 2001 at 02:40:22PM +0100, Ronald van der Pol wrote: > On Wed, 24 Jan 2001, Matt Dillon wrote: > > (I have cc-ed [EMAIL PROTECTED]) > > This came up about half a year ago in the KAME snap mailing list. > I think the conclusion was: a migration from "old" RPC to TI-RPC > is a pre-requisite for making NFS IPv6 aware. > > So, I was wondering whether a switch to TI-RPC is planned. I know > it is a major task. I don't think this is within the KAME-project scope. On NetBSD, the NetBSD crowd has done this almost a year ago (I believe) and NFS over IPv6 works just great on NetBSD. I'd guess FreeBSD could borrow a lot from the NetBSD work, reducing the major-ness of the task? Feico. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: status of bridge code
On Wed, 24 Jan 2001, Julian Elischer wrote: ... > > my dc cards. No problems so far - as long as I don't use DUMMYNET with it. > > I really wish I could use DUMMYNET as I need to put bandwidth limits on a > > few of the computers on my network. ... > Rate limitting is one thing that isn't there yet. If we pulled our fingers out, > I guess we would have ripped the dummynet rate limmiter out of where it is > and placed it into a netgraph node where it would be generally useful > instead of being hardcoded into one (sometimes useful) localtion in the > netoworking stacks. > > there is a rate limitter based on netgraph available from: > http://www.riss-telecom.ru/~vitaly/ > > but I have not tried it. > > I need to look at it again as I believe it has improved and > may be generally useful. > When I looked at it last it was a bit alpha. > It probably needs rewriting for the new netgraph API in -current. Current state of this project: Grade: production, working on more than 40 hosts from June 2000, city-wide ISP network OS version:3-STABLE from 8 January 2000 - this version currently used in our production routers/hosts Capabilities: guaranteed low bandwidth, maximum bandwidth, priority can be set for queue, traffic classification and bandwidth management realized by separate netgraph nodes. Since I currently have high workload, I dont have time to port it to 4.x or 5-CURRENT... Conclusion: volunteer required for this work... and I can consult him/her. -- Vitaly Belekhov System architect, AB-Telecom, Novosibirsk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
TI-RPC, IPv6 and NFS (was: Re: strong recommendation re: NFS)
On Wed, 24 Jan 2001, Matt Dillon wrote: > :On Sun, 21 Jan 2001, Matt Dillon wrote: > : > :> Concentrate on making the general network stack (aka TCP) and > :> filesystems SMP aware. Leave NFS alone for now. Please. > : > :If I understand correctly another item on the wishlist is TI-RPC > :(so that NFS can be made IPv6 aware). What is the latest on that? > : > : rvdp > > I don't think anyone is working on IPV6 issues at the moment. (I have cc-ed [EMAIL PROTECTED]) This came up about half a year ago in the KAME snap mailing list. I think the conclusion was: a migration from "old" RPC to TI-RPC is a pre-requisite for making NFS IPv6 aware. So, I was wondering whether a switch to TI-RPC is planned. I know it is a major task. rvdp To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bootstrapping issues with groff(1)
Hi!
Attached is the patch for RELENG_4. It works but I don't like
how it pollutes the Makefile.inc1. Anyone with a better idea?
On Tue, Dec 12, 2000 at 09:43:55AM -0800, Marcel Moolenaar wrote:
> Ruslan Ermilov wrote:
> >
> > > Let me rephrase the question: Did you modify the manpages to get it to
> > > work with the new groff(1) or is the new groff(1) backward compatible
> > > with the old groff(1)?
> > >
> > The new groff(1) is not always backwards compatible.
>
> Ok, thanks. That's all I wanted to hear.
>
> > OK, I will augment the USRDIRS then, add the groff to bootstrap-tools,
> > and leave the better (if one exists) implementation to someone else.
>
> Works for me.
>
> thanks,
>
> --
> Marcel Moolenaar
> mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
> tel: (408) 447-4222
On Wed, Jan 24, 2001 at 06:27:29PM +0100, [EMAIL PROTECTED] wrote:
> Hi. did you get any chance to fix the problem discussed earlier yet?
>
> I'm currently trying to buildworld on sources gootten with CVSup, using
> this supfile:
>
> # Defaults that apply to all the collections
> *default host=cvsup.FreeBSD.org
> *default base=/usr
> *default prefix=/usr
> *default release=cvs tag=RELENG_4
> *default delete use-rel-suffix
> *default compress
>
> ## The international secure collections.
> src-all
>
> buildworld fails as follows;
>
> ===> share/doc/usd/12.vi/summary
> touch _stamp.extraobjs
> (cd
> /usr/src/share/doc/usd/12.vi/summary/../../../../../contrib/nvi/docs/USD.doc/vitut;
> groff -mtty-char -Tascii -t -ms -o1-
>
>/usr/src/share/doc/usd/12.vi/summary/../../../../../contrib/nvi/docs/USD.doc/vitut/vi.summary)
> | gzip -cn > summary.ascii.gz
> ===> share/doc/usd/13.viref
> (cd
> /usr/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref;
> sed -e\ 's:\(\.so[\ \ ][\ \
>
>]*\)\(vi.ref\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:'
> -e\ 's:\(\.so[\ \][\ \
>
>]*\)\(ex.cmd.roff\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:'
> -e\ 's:\(\.so[\ \][\ \
>
>]*\)\(ref.so\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:'
> -e\ 's:\(\.so[\ \][\ \
>
>]*\)\(set.opt.roff\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:'
> -e\ 's:\(\.so[\ \ ][\ \
>
>]*\)\(vi.cmd.roff\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:'
> -e 's:^\.so index.so$::' vi.ref) | groff -mtty-char -Tascii -t -s -me -U
> -o1- > /dev/null
> groff: illegal option -- U
> usage: groff [-abehilpstvzCENRSVXZ] [-Fdir] [-mname] [-Tdev] [-ffam]
> [-wname]
>[-Wname] [ -Mdir] [-dcs] [-rcn] [-nnum] [-olist] [-Parg] [-Larg]
>[files...]
> groff -h gives more help
> *** Error code 1
>
> Stop.
>
> Can you please help me out here?
>
>
> On Sat, Dec 16, 2000 at 05:15:26PM +0200, Ruslan Ermilov wrote:
> > On Sat, Dec 16, 2000 at 01:28:16PM +0100, [EMAIL PROTECTED] wrote:
> > > Hi.
> > >
> > > I'm having a hell of a time upgrading my 3.4-STABLE box to 4.2-STABLE.
> > > My latest blues concern groff, for which I saw you posting a patch on
> > > the freeBSD questions mailing list on the 9th of December.
> > >
> > > I hope this patch solved the problem, I did not see any messages on that.
> > >
> > > Unfortunately, you do not post instructions to apply the patch. I'm hoping
> > > to get them out of you via this email ;-)
> > >
> > I am planning to commit the fix to 5.0-CURRENT and 4.2-STABLE shortly.
> > I will send you a notice after I do this.
> >
> > --
> > Ruslan Ermilov Oracle Developer/DBA,
> > [EMAIL PROTECTED] Sunbay Software AG,
> > [EMAIL PROTECTED] FreeBSD committer,
> > +380.652.512.251Simferopol, Ukraine
> >
> > http://www.FreeBSD.org The Power To Serve
> > http://www.oracle.com Enabling The Information Age
--
Ruslan Ermilov Oracle Developer/DBA,
[EMAIL PROTECTED] Sunbay Software AG,
[EMAIL PROTECTED] FreeBSD committer,
+380.652.512.251Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
Index: Makefile.inc1
===
RCS file: /home/ncvs/src/Makefile.inc1,v
retrieving revision 1.141.2.19
diff -u -p -r1.141.2.19 Makefile.inc1
--- Makefile.inc1 2001/01/22 23:26:15 1.141.2.19
+++ Makefile.inc1 2001/01/25 12:16:07
@@ -168,6 +168,8 @@ CROSSENV= MAKEOBJDIRPREFIX=${OBJTREE} \
COMPILER_PATH=${WORLDTMP}/usr/libexec:${WORLDTMP}/usr/bin \
LIBRARY_PATH=${WORLDTMP}${SHLIBDIR}:${WORLDTMP}/usr/lib \
OBJFORMAT_PATH=${WORLDTMP}/usr/libexec \
+ GROFF_FONT_PATH=${WORLDTMP}/usr/share/groff_font \
+ GROFF_TMAC_PATH=${WORLDTMP}/usr/share/tmac \
PERL5LIB=${WORLDTMP}/usr/libdata/perl/5.00503
# bootstrap-too
Re: status of bridge code
>personally I use the netgraph bridging code and I think (though I'm biased) >that you should look at using htat rather than the hardwired bridging >code that it was derived from. Now that I've read up on it I can tell you you and and Archie have every right to be biased =) I've had a netgraph bridge in place for a while now and it works very well. (On 4.X-STABLE, on 5.X-CURRENT it went kablooie. See panic trace) > > item on my list. Being an allround good networking OS this is unacceptable > > IMHO. > >Have a look at what you can do with netgraph first. > >Most people don't know what it is but it allows almost arbitrarily >complicated network topologies to be set up from the command line. What you might want to tell people is that it allows networking structures to be setup in a simple manner, but is so powerful it can also be used for immensely complex structures. A friend and fellow BSD user of mine's first response was "I like to keep things simple". After I rephrased into the above he was much more interested. But from my list of wishes I'd say the first 3 are gone. All that's left is spanning tree. I'm probably going to need this pretty soon, so once more I'm asking if anyone is working on it. If not I'll start on it. Also, a quick question for you netgraph guys. Why is it that ng_one2many send a packet only out of one hook? I can see use for an algorithm that sends packets from the 'one' hook to all the 'many' hooks (that are up) and keep the normal behaviour for many to one. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
