Can we use this for the JDK? (was: Motif goes open source)
Dear all, Is there someone on this list who's into the finer points of copyrighting? I would like to know what the implications are of this for the soon-to-be-coming native FreeBSD JDK port. In what form is Motif going to be available to the general FreeBSD developer? Am I going to find /usr/ports/x11-toolkits/motif anytime soon, or is this going to be more complicated than that? In what form would we have to distribute this with our JDK port (Java/SCCL-legalities aside)? Kees Jan == You are only young once, but you can stay immature all your life To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Can we use this for the JDK? (was: Motif goes open source)
"Koster, K.J." wrote: Dear all, Is there someone on this list who's into the finer points of copyrighting? I would like to know what the implications are of this for the soon-to-be-coming native FreeBSD JDK port. In what form is Motif going to be available to the general FreeBSD developer? Am I going to find /usr/ports/x11-toolkits/motif anytime soon, or is this going to be more complicated than that? As Poul-Henning Kamp noted earlier we have licenses in the ports tree that are *much* stranger than this one. I'd be very surprised if we don't see an entry in ports/x11-toolkits for Motif sometime soon. I'd also be very interested in what the "Hungry Programmers" have to say about this new development. All in all, I think this was a good day for open-source software. :-) Cheers, Jerry Hicks [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Com Port Issue
Hello, I wrote a samll program to get weather from a Davis Net weather station attached to a com port (/dev/cuaa0) in this case. It worked on Linux and IRIX, I am wondering why it compiles and runs, but does not get any data back from the device in FreeBSD. A minimal program that just listens for a ACK (\006) from the station can be seen at http://east.dhs.org/test11.c If you know someone that could help me resolve this issue, please let me know. Thanks. Derick J. Fernano To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Cyclades Cyclom YeP PCI problem
Hi, I have two cyclom YeP PCI board installed with 32 serials ports connected to both on a FreeBSD 4.0 release system. The first board (cy0) is working without problems however the second one (cy1) give some trouble. When I try to connect to a port e.g. cuac10 - cuac1v a kernel warning is displayed: 'WARNING: driver cy should register devices with make_dev () (dev_t = "cy/0x1008f")' but the connected is made. I added some 'printf ()'s to the 'cy.c' file in the 'cyattach_common ()' to verify whether 'make_dev ()' is called for the relevant ports and that seems to be OK. So my question is what wrong here? Can someone give a hint? Thanks, Arjan Knepper begin:vcard n:Knepper;Arjan tel;fax:+31-(0)10-243-7314 tel;work:+31-(0)10-243-7362 x-mozilla-html:FALSE url:http://www.jak.nl org:JAK++ Software Development B.V. adr:;;Stoveer 247;Rotterdam;;3032 GB;Netherlands version:2.1 email;internet:[EMAIL PROTECTED] x-mozilla-cpt:;-7904 fn:Arjan Knepper end:vcard
Motif porting discussions on -java
Just to let the non-java hackers know, there is some Motif porting discussion going on on freebsd-java. You may want to have a looksee there if you're working on Motif too. :) Kees Jan == You are only young once, but you can stay immature all your life To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
3.4 make world dies on groff
Dear Hackers, I have the problem that make world does not grok groff. Please find the final messages of the compilation at the end of this e-mail. I've cvsupped last night, just before the "make world", so I guess my source tree must be sane. I've disabled softupdates, and -pipe, but that makes no difference. I assume that something in my box is seriously broken. I don't think it's hardware, because it dies reproducably at the exact same spot under different loads (i.e. I ran some other compiles in parallel with the make world, and I saw no other strangeness.) What can I do to get groff to build for me? Kees Jan == You are only young once, but you can stay immature all your life c++ -I/usr/obj/usr/src/tmp/usr/include/g++ -O -I/usr/src/gnu/usr.bin/groff/troff/../include -fno-for-scope -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_STDLIB_H=1 -DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1 -DSTDIO_H_DECLARES_POPEN=1 -DSTDIO_H_DECLARE_PCLOSE=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DSYS_SIGLIST_DECLARED=1 -I/usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/include -fno-for-scope -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/env.cc c++ -I/usr/obj/usr/src/tmp/usr/include/g++ -O -I/usr/src/gnu/usr.bin/groff/troff/../include -fno-for-scope -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_STDLIB_H=1 -DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1 -DSTDIO_H_DECLARES_POPEN=1 -DSTDIO_H_DECLARE_PCLOSE=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DSYS_SIGLIST_DECLARED=1 -I/usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/include -fno-for-scope -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/node.cc c++ -I/usr/obj/usr/src/tmp/usr/include/g++ -O -I/usr/src/gnu/usr.bin/groff/troff/../include -fno-for-scope -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_STDLIB_H=1 -DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1 -DSTDIO_H_DECLARES_POPEN=1 -DSTDIO_H_DECLARE_PCLOSE=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DSYS_SIGLIST_DECLARED=1 -I/usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/include -fno-for-scope -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/input.cc /usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/input.cc: In function `static void input_stack::end_file()': /usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/input.cc:56 6: Internal compiler error. /usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/input.cc:56 6: Please submit a full bug report to `[EMAIL PROTECTED]'. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
ECP code
Is there any ECP code anywhere besides the /usr/src/sys/dev/ppbus directory? I'm trying to trak down why ECP doesn't work undder 4.0. So, far, i can't find any significant differences, other than the newbus function calls. Where does the ECP status get reported, and where is the ECP transfer actually handled? jm -- --- Jonathon McKitrick -- [EMAIL PROTECTED] I am a bomb technician. If you see me running, try to keep up. --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
SSE support for FreeBSD
I add SSE support for FreeBSD 4.0-RELEASE and 5.0-CURRENT. Some more work is needed everything to go well, but it works functionally now. The patches and documents are avaiable at: http://home.jp.freebsd.org/~issei/sse/sse.html Limitations: - Multiprocessor system is not supported. - There is no exception handler to deal with SSE Exceptions. - No spaces are available for SSE registers in struct fpregs. So, we cannot record SSE registers when dumping core, nor access to SSE registers via procfs. Comments, bug reports etc. are welcome. Issei.- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Motif porting discussions on -java
"Koster, K.J." wrote: Just to let the non-java hackers know, there is some Motif porting discussion going on on freebsd-java. You may want to have a looksee there if you're working on Motif too. :) Seems, that nobody made a port upto now :-) So, here are my experiences with openmotif. There is a problem with motif's own version of imake. You can copy imakemdep.h from xfree's imake or just use XFree's imake itself. Copy/link Imake.tmpl, Motif.rules and Motif.tmpl (from config/cf) to /usr/X11R6/lib/X11/config for that. And now it gets tricky. lib/Xm/TextF.c needs some wide-charachter functions, that are not present in our libc. You can find a lib with these functions here: http://www.cs.rpi.edu/~crossd/FreeBSD/wcs-19990606.tar.gz I got the needed functions and just copied into the motif- sourcefile. Ah. For shared libs. You need to make the symlinks from libXX.so.a.b to libXX.so manually, if you don't do it, the linker will take the static libs. Well, thats an evil hack, but it gets you started until someone with more time and knowledge makes a "good" port :-) Enjoy. -- Tom To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Motif porting discussions on -java
Thomas Runge [EMAIL PROTECTED] wrote: "Koster, K.J." wrote: Just to let the non-java hackers know, there is some Motif porting discussion going on on freebsd-java. You may want to have a looksee there if you're working on Motif too. :) Seems, that nobody made a port upto now :-) So, here are my experiences with openmotif. There is a problem with motif's own version of imake. You can copy imakemdep.h from xfree's imake or just use XFree's imake itself. Copy/link Imake.tmpl, Motif.rules and Motif.tmpl (from config/cf) to /usr/X11R6/lib/X11/config for that. If Motif has it's own version of imake, make sure it uses gcc -E (or /usr/bin/cpp) instead of /usr/libexec/cpp. -- Dan Eischen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: need to borrow a clue re: rtld
In article [EMAIL PROTECTED], Jacques A . Vidrine [EMAIL PROTECTED] wrote: Messing about with Dante (the SOCKS5 replacement), I've encountered some difficulty with run-time linking that I don't understand. In brief: $ env LD_PRELOAD=libdsocks.so telnet # works $ env LD_PRELOAD=libdsocks.so xchat # undefined symbol '_gethostbyname' $ env LD_PRELOAD=libc.so:libdsocks.so xchat # works Which version of FreeBSD? If you have time, please rebuild "src/libexec/rtld-elf" with DEBUG_FLAGS=-DDEBUG. Make a copy of your existing "/usr/libexec/ld-elf.so.1" and then install the debugging version. Run your first test case like this: script Log.1 env LD_DEBUG=1 LD_PRELOAD=libdsocks.so telnet (exit telnet and get out of "script") and likewise for the failing test case (with a different filename for script, of course). Send the output to me and I'll try to figure out what's happening. After you're done, you should restore your original (non-debugging) rtld. It's more efficient and also probably more secure. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: need to borrow a clue re: rtld
On Tue, May 16, 2000 at 09:37:44AM -0700, John Polstra wrote: Which version of FreeBSD? 4.0-STABLE ~ May 8. If you have time, please rebuild "src/libexec/rtld-elf" with DEBUG_FLAGS=-DDEBUG. [logs for telnet and xchat sent off-list] I should have mentioned earlier that in the fail case, xchat operates until it tries to connect to a server (i.e. when you push the connect button), as opposed to failing during the initial loading of libraries. Thanks for helping with this! -- Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: mktemp() vs. mkstemp()
Alfred Perlstein wrote: * Wes Peters [EMAIL PROTECTED] [000515 12:11] wrote: Kris Kennaway wrote: On Sun, 14 May 2000, Tim Vanderhoek wrote: It's certainly not like it would be the first non-portable function we've added. Where adding functions to libraries encourages better coding practices, I'm (often) in favour of it, especially if it encourages more secure coding practices. Ultimately everyone benefits, and the pain is short-term. True, but I'd venture that in most of those cases they did something a little less trivial than one line of code. We could simply redefine mktemp to not be such a security hole. Do common programs that use mktemp depend on side effects? The side effect they depend on is that the char * returned is unique, but since no file was created it's not garanteed so. You can't fix it. Drat, that's right. Anyone wanna pollute the kernel and filesystem layers with a "reserve this filename" function? That sounds fugly, doesn't it? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
de-GNUfication of Digiboard driver ?
Hi, I've been reading recently some stories about the licensing issues and that brought me to an interesting conclusion: apparently, we are able to change the license of the Digiboard driver from GPL to BSD ? It does not seem to be that much important any more as these cards are obsolete, but still. I was the original author of that driver. To get the information about the Digi interface I've read the Linux driver. I supposed that it made me mentally contaminated with GPL. But all the FreeBSD driver was written from scratch, with none of the Linux code re-used (except for the array with the image of firmware but apparently that one was available as well from non-GPL-contaminated sources, such as Digi's drivers for other Unixes). But now looking at the BSD-USL case it seems like I was wrong about the mental contamination. Apparently none of the author of the later changes to this driver were enthusiastic about GPL as well. So if I'm getting the things right, can we just go ahead now and change its license to BSD ? Or am I wrong ? -SB To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Motif paging
It's been a while since I used mwm. I installed the OpenMotif Metrolink
binaries and have mwm running. It's just as solid as I remember it. One
problem I cannot get paging to work. On an old system I used to use the
following worked for paging:
.Xdefaults
---
Mwm*windowMenu: MyWindowMenu
Mwm*bitmapDirectory:/usr/X11R6/include/X11/icons
!*** panning stuff *
! setup toggle_pinstate menu entry...
! NOTE - these pixmaps require fully qualified path names...
! see sample.mwmrc file for compete definition.
Mwm*pinStateLabelType: PIXMAP
Mwm*pinnedPixmap: pinned
Mwm*unpinnedPixmap: unpinned
! setup which clients and icons are pinned
Mwm*Mwm.clientPinned: True
Mwm*iconPinned:True
Mwm*xclock.clientPinned: True
! Setup the panning menu
Mwm*GotoMenuColor*packing: PACK_COLUMN
Mwm*GotoMenuColor*orientation: HORIZONTAL
Mwm*GotoMenuColor*alignment: ALIGNMENT_CENTER
! This stops all windows from being repositioned on-screen
! after a restart.
Mwm*positionOnScreen: False
.mwmrc
# Menu for hopping to different locations on the virtual desktop.
# The images should be kept in the location specified by
# the "Mwm*bitmapDirectory:" resource.
# See sample images in the images directory. The following
# image references refer to bitmaps and pixmaps contained in
# the examples/images/ directory.
Menu GotoMenuColor
{
link f.goto 0,0
mail f.goto 0,2000
book.2 f.goto 0,4000
knifef.goto 0,6000
plugin f.goto 0,8000
}
# Default Window Menu Description
Menu MyWindowMenu
{
@pinned f.toggle_pin_state
Restore _R AltKeyF5 f.normalize
Move_M AltKeyF7 f.move
Size_S AltKeyF8 f.resize
Minimize_n AltKeyF9 f.minimize
Maximize_x AltKeyF10 f.maximize
Refresh _f AltKeyF2 f.refresh_win
Lower _L AltKeyF3 f.lower
no-labelf.separator
Close _C AltKeyF4 f.kill
}
#
# key binding descriptions
#
Keys DefaultKeyBindings
{
ShiftKeyEscapewindow|icon f.post_wmenu
MetaKeyspace window|icon f.post_wmenu
MetaKeyTabroot|icon|windowf.next_key
Meta ShiftKeyTab root|icon|windowf.prev_key
MetaKeyEscape root|icon|windowf.circle_up
Meta ShiftKeyEscape root|icon|windowf.circle_down
Meta Shift CtrlKeyexclam root|icon|windowf.set_behavior
MetaKeyF6 window f.next_key transient
Meta ShiftKeyF6 window f.prev_key transient
KeyF4 iconf.post_wmenu
Meta ShiftKeyDelete root|icon|windowf.restart
AltKeyF10 root|window|iconf.post_rmenu
CtrlKeyEscape root|window|iconf.normalize_and_raise_iconbox
MetaKeyUp window|root|iconf.pan 0,-100,1
MetaKeyDown window|root|iconf.pan 0,100,1
MetaKeyLeft window|root|iconf.pan -100,0,1
MetaKeyRight window|root|iconf.pan 100,0,1
}
#
# button binding descriptions
#
Buttons DefaultButtonBindings
{
Btn1Down frame|icon f.raise
Btn3Down frame|icon f.lower
Btn1Down rootf.menu Clients
Btn2Down rootf.menu GotoMenuColor
Btn3Down rootf.menu Control
MetaBtn1Down window|icon f.move
MetaBtn2Down window|icon f.resize
Meta ShiftBtn1Downwindow|icon f.minimize
Meta ShiftBtn2Downwindow|icon f.focus_color
Meta ShiftBtn3Downwindow|icon f.post_wmenu
MetaBtn1Down rootf.track_pan
MetaBtn2Down rootf.track_pan
}
Can anyone help me with this or direct me to a place with the info?
Regards,
--
Ted Sikora
Jtl Development Group
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Can we use this for the JDK? (was: Motif goes open source)
W Gerald Hicks wrote: "Koster, K.J." wrote: In what form is Motif going to be available to the general FreeBSD developer? Am I going to find /usr/ports/x11-toolkits/motif anytime soon, or is this going to be more complicated than that? As Poul-Henning Kamp noted earlier we have licenses in the ports tree that are *much* stranger than this one. I'd be very surprised if we don't see an entry in ports/x11-toolkits for Motif sometime soon. I'd also be very interested in what the "Hungry Programmers" have to say about this new development. http://www.lesstif.org/future.html Basically, LessTif is still a viable/valuable toolkit because you can't use Open Motif on any proprietary OS. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: mktemp() vs. mkstemp()
In message [EMAIL PROTECTED], Wes Peters writes: Drat, that's right. Anyone wanna pollute the kernel and filesystem layers with a "reserve this filename" function? That sounds fugly, doesn't it? That's why I suggested a simpler solution even I can code :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
smb printer trouble
I wrote a simple filter to print to an nt print queue through the smbclinet. It tests to see if the file is postscript or text, and if it is text it sends a control code to tell the printer to do the lf-crlf conversion. My problem is that the '\' escapes in the first line get clobbered. for example, if I print this printcap: begin printcap lp:\ :sh:\ :lp=/dev/lpt0:\ :sd=/var/spool/output/lpd/lp:\ :lf=/var/log/lpd/lpd.log: lplaser:\ :sh:\ :lp=/dev/null:\ :if=/root/filters/smb-filter:\ :sd=/var/spool/output/lpd/lplaser:\ :lf=/var/log/lpd/lpd.log: end printap the entire entry for "lp" will be on one line, but the "lplaser" entry will print out like it is supposed to. I know why it is doing it, however I don't know how to fix it. Any help will be appreciated (script is below). Thanks, James begin smb-filter #!/bin/sh # Input filter to print to a NT print queue, requires smbclient. # # Author: James Halstead, e-mail: [EMAIL PROTECTED] # # Read stdin to a temp, make sure to determine the print type, then use # smbclient to print to the nt queue. SERVER=SERVER NAME PRINTER=cwPRINTER NAME TEMP=/tmp/smbprint TEMP=`mktemp -q $TEMP.XX` read firstline first_two=`expr "$firstline" : '\(..\)'` if [ "$first_two" != "%!" ]; then printf "\033k3G" $TEMP fi #lets see, copy the firstline to temp, cat the rest to the temp, # make one ugly command to print the file to the smb printer then # rm the temp file. echo "$firstline" $TEMP cat $TEMP \ /usr/local/bin/smbclient $SERVER\\$PRINTER -UGUEST -N\ -c"print $TEMP" \ rm -f $TEMP /dev/null exit 0 exit 1 end smb-filter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ECP code
Is there any ECP code anywhere besides the /usr/src/sys/dev/ppbus directory? I'm trying to trak down why ECP doesn't work undder 4.0. So, far, i can't find any significant differences, other than the newbus function calls. Where does the ECP status get reported, and where is the ECP transfer actually handled? It's in the ppc driver (sys/isa/ppc.c). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ECP code
On Tue, May 16, 2000 at 12:44:26PM -0700, Mike Smith wrote: Is there any ECP code anywhere besides the /usr/src/sys/dev/ppbus directory? I'm trying to trak down why ECP doesn't work undder 4.0. So, far, i can't find any significant differences, other than the newbus function calls. Where does the ECP status get reported, and where is the ECP transfer actually handled? It's in the ppc driver (sys/isa/ppc.c). Where was it before? I could look for it at home, but right now i'm searching on a remote 3.4 machine, and i can't find it. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: mktemp() vs. mkstemp()
In message [EMAIL PROTECTED] Wes Peters writes: : Drat, that's right. Anyone wanna pollute the kernel and filesystem : layers with a "reserve this filename" function? That sounds fugly, : doesn't it? Yes. It isn't needed. mkstemp already does the looping to make it safe. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ECP code
On Tue, May 16, 2000 at 12:44:26PM -0700, Mike Smith wrote: Is there any ECP code anywhere besides the /usr/src/sys/dev/ppbus directory? I'm trying to trak down why ECP doesn't work undder 4.0. So, far, i can't find any significant differences, other than the newbus function calls. Where does the ECP status get reported, and where is the ECP transfer actually handled? It's in the ppc driver (sys/isa/ppc.c). Where was it before? I could look for it at home, but right now i'm searching on a remote 3.4 machine, and i can't find it. 'locate ppc.c' is your friend. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
IPv6 and hosts.allow
Is inetd wrapping and hosts.allow supposed to support IPv6 addresses? Because it isn't for me. Not only that but added an IPv6 address to hosts.allow seems to prevent processing of IPv4 anddress on that line. If it should and is broken I will submit a PR. If not I will look and see if I can submit a PR with code. BTW this is 4.0 cvsupd and compile with cvs-cur-6351.gz of this morning (2000/5/16) Jim -- Studies show that 1 out of every 4 Americans suffer some form of mental illness. So look at your three best friends, if they are okay it is YOU! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ECP code
I just realized i think this machine may not have that part of the source installed. Also, the ppc code is even more complex than the ppbus stuff. I don't know how much good i'll be able to do. Does anyone have any ideas on figuring out why ECP is broken? Is it broken in -current as well? jm -- --- Jonathon McKitrick -- [EMAIL PROTECTED] I am a bomb technician. If you see me running, try to keep up. --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: IPv6 and hosts.allow
On Tue, 16 May 2000 16:10:28 -0400 James Housley [EMAIL PROTECTED] said: jim Is inetd wrapping and hosts.allow supposed to support IPv6 addresses? jim Because it isn't for me. Not only that but added an IPv6 address to jim hosts.allow seems to prevent processing of IPv4 anddress on that line. jim If it should and is broken I will submit a PR. If not I will look and jim see if I can submit a PR with code. BTW this is 4.0 cvsupd and compile jim with cvs-cur-6351.gz of this morning (2000/5/16) Yes, I wrote IPv6 support code for tcp_wrappers. And, actually, I'm using it. How do you specify IPv6 address? IPv6 address has `:' in it and it conflict with tcp_wrappers's field separator. So, you need to wrap IPv6 address with `[' and `]'. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.imasy.org/~ume/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: IPv6 and hosts.allow
"Hajimu UMEMOTO ($BG_K\(B $BH%(B)" wrote: Yes, I wrote IPv6 support code for tcp_wrappers. And, actually, I'm using it. How do you specify IPv6 address? IPv6 address has `:' in it and it conflict with tcp_wrappers's field separator. So, you need to wrap IPv6 address with `[' and `]'. Like this? Would you like me to submit a PR with this or can you commit the changes or better ones??? Jim -- Studies show that 1 out of every 4 Americans suffer some form of mental illness. So look at your three best friends, if they are okay it is YOU! --- hosts.allow Fri May 5 13:58:34 2000 +++ hosts.allow.new Tue May 16 16:34:05 2000 @@ -33,6 +33,8 @@ # name) *MUST* be specified for portmap(8). ALL : localhost 127.0.0.1 : allow ALL : my.machine.example.com 192.0.2.35 : allow +# To use IPv6 addresses you must enclose them in []'s +ALL : [fe80::/10] # Sendmail can help protect you against spammers and relay-rapers sendmail : localhost : allow
newbus documentation
Hello! I've started a newbus introduction. It covers most aspects of a newbus driver, based on Warner Losh's led-driver. I've added interrupts- and ioctl-handlers. The whole thing "behing" newbus is a little bit vague. Please review my documentation and give me hints for improvements. I'd like to see that introduction in the official docs some time, since I've heard from several people that the bad thing with newbus is its lack of documentation. ftp://big.endian.de/pub/FreeBSD/newbus-intro.tar.gz Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Motif goes open source
Sam Stephenson wrote: On Monday, May 15, 2000 at 03:09a, Bob Bishop [EMAIL PROTECTED] wrote: "The Open Group, a vendor and technology-neutral consortium dedicated to enterprise integration, announced today that it is releasing the source code of Motif, using a public license, to the Open Source community." Full details at http://www.opengroup.org/openmotif Check out the web page: "We want to support the momentum of Open Source operating systems such as Linux(R) and FreeBSD by developing an Open Motif(R)..." and "UNIX and Motif are registered trademarks of The Open Group in the US and other countries. The Open Group and the X Window System are trademarks of The Open Group. Linux is a registered trademark of Linus Torvalds." Sorry, it's not anymore. There are two registrations for the simple trademark "Linux", including: Rosch, AG (Swiss) for laundry detergents and laundry bleaches for home use; cleaning preparations for home use; degreasing preparations for home use; general purpose scouring powders; skin soap for personal use; perfume; essential oils for personal use; preparations for personal hygiene and cosmetic purposes, hair tonic; toothpaste. Croce, William R. Della, Jr., 33 Snow Hill St. Boston MA 02113 computer operating system software to facilitate computer use and operation. CHANGE IN REGISTRATION HAS OCCURRED. I prefer to use the first because it amuses me. Correct me if I'm wrong, but I do believe FreeBSD is a registered trademark of some organization -- FreeBSD, Inc., Walnut Creek, or BSDI. Someone should politely inform The Open Group of FreeBSD's trademark status. WALNUT CREEK CDROM, INCORPORATED 1547 Palos Verdes Mall, Suite 260 Walnut Creek CALIFORNIA 94596 I see no reason you shouldn't inform them yourself. Do you? http://trademarks.uspto.gov/cgi-bin/search4?ENG+3 -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ECP code
On Tue, May 16, 2000 at 01:33:34PM -0700, Mike Smith wrote: Also, the ppc code is even more complex than the ppbus stuff. I don't know how much good i'll be able to do. Does anyone have any ideas on figuring out why ECP is broken? Is it broken in -current as well? No ideas, no. You should be able to fathom at least parts of the code, although you may well end up needing a copy of the 1284 spec. You might also look at the linux code for inspiration. Well, i can follow things somewhat, but without a list of all the functions and what they do, it's tough to get your bearings. Maybe that's what i should do. Also, i can't tell what relates to the zip drive and what doesn't. The 1284 does, you say? I'll check out the old imm.c driver as well. Thanks. But i don't know if the problem is the driver or the ECP part of the interface. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Cyclades Cyclom YeP PCI problem
1.) The problem with the cy driver resides in the function cyattach_common in the cy.c file. make_dev is called like this: make_dev(sio_cdevsw, unit, UID_ROOT, GID_WHEEL , 0600, "ttyc%r%r", adapter, unit % CY_MAX_PORTS); where 'unit' is 0 to 31 for board one 32 to 63 for board two 64 to 95 for board three 96 to 127 for board four. But when I use 'MAKEDEV cuacX' for the installed and configured cy devices, MAKEDEV does the following: minor='ttyminor $unit' minor='expr $card \* 65536 + $minor' The second argument in make_dev function needs a conversion something like : make_dev(sio_cdevsw, ( adapter * 65536 + ( unit % CY_MAX_PORTS ) ), UID_ROOT, GID_WHEEL , 0600, "ttyc%r%r", adapter, unit %CY_MAX_PORTS); 2.) For some reason there is sometimes a problem with detecting the CD1400 ic's firmware_revision. I solved it by increasing the DELAY values in a loop and inserted some (extra) loops and check's, but I don't know whether or not it might hurt at some point? Arjan Knepper I have two cyclom YeP PCI board installed with 32 serials ports connected to both on a FreeBSD 4.0 release system. The first board (cy0) is working without problems however the second one (cy1) give some trouble. When I try to connect to a port e.g. cuac10 - cuac1v a kernel warning is displayed: 'WARNING: driver cy should register devices with make_dev () (dev_t = "cy/0x1008f")' but the connected is made. I added some 'printf ()'s to the 'cy.c' file in the 'cyattach_common ()' to verify whether 'make_dev ()' is called for the relevant ports and that seems to be OK. So my question is what wrong here? Can someone give a hint? begin:vcard n:Knepper;Arjan tel;fax:+31-(0)10-243-7314 tel;work:+31-(0)10-243-7362 x-mozilla-html:FALSE url:http://www.jak.nl org:JAK++ Software Development B.V. adr:;;Stoveer 247;Rotterdam;;3032 GB;Netherlands version:2.1 email;internet:[EMAIL PROTECTED] x-mozilla-cpt:;-7904 fn:Arjan Knepper end:vcard
Re: IPv6 and hosts.allow
On Tue, 16 May 2000 16:37:07 -0400 James Housley [EMAIL PROTECTED] said: How do you specify IPv6 address? IPv6 address has `:' in it and it conflict with tcp_wrappers's field separator. So, you need to wrap IPv6 address with `[' and `]'. jim Like this? No. For example: ALL : [fe80::]/10 Please see manpage for host_access(5). jim Would you like me to submit a PR with this or can you commit jim the changes or better ones??? jim +# To use IPv6 addresses you must enclose them in []'s jim +ALL : [fe80::/10] To add example in /etc/hosts.allow is good idea. But, use of link-local address is not so good. Because, current IPv6 implementation of tcp_wrappers cannot treat scope-id. So, this means: allow any link-local connections from any neighbor networks It contains not only ethernet but also gif tunnel etc. Do you really need to allow link-local connection? I already rewrote tcp_wrappers to support scoped address and it is shipped as KAME ports. You can obtain it from: http://www.imasy.or.jp/~ume/ipv6/tcp_wrappers_7.6-ipv6-1.9.diff.gz By using this, you can specify: ALL : [fe80::%de0]/10 : allow But, this has some limitations. This is a patch to original tcp_wrappers. And, this doesn't work on 5.0-CURRENT nor 4.0-STABLE due to getaddrinfo() problem around treatment of IPv4 address obtained by specifying PF_UNSPEC. To work it on FreeBSD without additional KAME package, we should correct getaddrinfo(). The patch is ready and now in review. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.imasy.org/~ume/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: What do people think of maybe using the sourceforge software?
I guess that most people leading a project could do with a bit of feature creep, features being shoved under their noses. Even if at first you think that source control solves all our problems, it still could be a way to develop new tools and get them running and tried out before committing them to the tree. Second, the projects page we have now, with all due respect to the people that try to keep it reasonably organised, is a mess due to the lack of updates. people only maintain their project pages perhaps, but certainly not the links that lead to them. Being able to work with more people on the same project on an equal bases would be a good idea IMHO. Nick http://sourceforge.net/project/filelist.php?group_id=1 Contains the software used by source forge to implement the project/help desk/download tracker thingie which they themselves use to manage the various projects registered with source forge. I think it's also reasonable to say that FreeBSD itself is a bit too large to register and run as a sourceforge project, but why not use the same software to offer a higher level of "polish" to the existing project infrastructure? Comments? I'm just playing with this stuff a bit myself right now and will say more once I actually know more about it. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Bad Block scan
I thought FreeBSD had an option on install to run a bad block scan on a drive? Just installed (4.0-RELEASE) and noticed it wasn't there. Any specific reason...or maybe a reference page that explains. Thanks in advance. Nick Rogness - Speak softly and carry a Gigabit switch. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Bad Block scan
On Tue, May 16, 2000 at 04:59:11PM -0600, Nick Rogness wrote: I thought FreeBSD had an option on install to run a bad block scan on a drive? Just installed (4.0-RELEASE) and noticed it wasn't there. Any specific reason...or maybe a reference page that explains. Thanks in advance. Bad block management was removed in 4.0. All modern drives (ATA and SCSI) do hardware bad block management and no one wanted to maintain the old code so it was killed. The general feeling is that if your disk generates errors it has run out of replacement sectors and thus is dying and should be replaced. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
enabling -DNAMEBLOCK breaks biosboot build (fwd)
Hello, I sent this to -questions but no one could help me. TIA if you can help me :-). With 3.4-STABLE code, cvsup'd on Tues May 9th, enabling -DNAMEBLOCK in /sys/i386/boot/biosboot/Makefile breaks the build: ... dd if=boot.nohdr of=boot2 bs=512 skip=1 14+1 records in 14+1 records out 7184 bytes transferred in 0.000439 secs (16362683 bytes/sec) boot2 is too big *** Error code 2 I'd like the NAMEBLOCK feature so I can use nextboot. Is there a new way to boot different kernels, or am I screwed? Thanks! :-) Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
4.0 will not send out UDP packets
Hi all, I've been having a number of problems with this 4.0 install. I'm running a program called ompages-dhid. It's a rewrite of the dhid.org client and server. My partner actually wrote it. He's a linux programmer and is trying to get this to work on free and open bsds... The openbsd port works fine, but the freebsd-4.0 port will not log to syslog, nor will it send out udp packets to server daemon. I'm getting the following messages. 'icmp-response bandwidth limit 350/200 pps' 'inetd[370] warning: can't get client address: Connection reset by peer' 'rlogind[370]: Can't get peer name of remote host: Socket is not connected' Any ideas. I could really use some help on this source code. If you can help me; I'll send you the source... it's open so that is not a problem.. Thanks... -nate -- Nate Puri, PresidentInstallation, Administration, Security BankofData.net (not yet live) and Support for Home and Small Networks... [EMAIL PROTECTED] One of The Wheel's Massive Holdings To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: What do people think of maybe using the sourceforge software?
On Tue, 16 May 2000, Nick Hibma wrote: I guess that most people leading a project could do with a bit of feature creep, features being shoved under their noses. Even if at first you think that source control solves all our problems, it still could be a way to develop new tools and get them running and tried out before committing them to the tree. Second, the projects page we have now, with all due respect to the people that try to keep it reasonably organised, is a mess due to the lack of updates. people only maintain their project pages perhaps, but certainly not the links that lead to them. Being able to work with more people on the same project on an equal bases would be a good idea IMHO. Nick Although I have no control over what goes on behind the curtains, I must say the following: My feeling is that a lot of the doc people are working really hard to make this sort of stuff happen. I know, for instance, that Jeroen (Asmodai) has great ideas in place for centralization of project listings, and TODO lists, etc. The only thing left is to bind these ideas together and make things like this happen. One of the big issues, I feel, is the duplication of efforts and I, as a "guy who develops from the sidelines" can tell you right now: a centralized information-base such as the one [I believe] these people are working on is key to what I choose to poke at next. Please remember that a lot of people who contribute to the project are not necessarily committers and do not read -commiters mail. The centralization of documentation and various other data will make collaboration possible and, best of all, it'll make it fun (which is what open source is about for many of us). With the centralization of information will come direction. Cheers, Bosko. -- Bosko Milekic * pages.infinit.net/bmilekic/index.html * www.technokratis.com [EMAIL PROTECTED] * [EMAIL PROTECTED] * [EMAIL PROTECTED] "Give a man a fish and he will eat for a day. Teach him how to fish, and he will sit in a boat and drink beer all day." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Com Port Issue
Derick Fernando wrote: Hello, I wrote a samll program to get weather from a Davis Net weather station attached to a com port (/dev/cuaa0) in this case. It worked on Linux and IRIX, I am wondering why it compiles and runs, but does not get any data back from the device in FreeBSD. A minimal program that just listens for a ACK (\006) from the station can be seen at http://east.dhs.org/test11.c If you know someone that could help me resolve this issue, please let me know. See /usr/ports/comm/mlan. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
