New 64 bit Compiler from SGI
For those interested , SGI has released their 64 bit compiler for Intel's Itanium. http://oss.sgi.com/projects/Pro64/ Enjoy -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Breaking build world costs $5? (was: Can we please have a current that compiles?)
Darren Reed wrote: Maybe the comitters ought to take an idea from many software companies and contribute $5 to the beer fund every time they break the build. Have it all come due at the next BSDcon to fund a committer beer bash. :-) I'd go along with that. What do the other committers think? Isn't this the "FreeBSD" project ? There is no such thing as a "free beer". If there are enough bad committs, we can start thinking in terms of parties with Free Beer and Pizza 8) -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Motif is now Open Source 8)
Check it out at: http://www.opengroup.org/openmotif/ "We want to support the momentum of Open Source operating systems such as Linux® and FreeBSD by developing an Open Motif® licence for use with Open Source operating systems." Also the OpenGroup is looking for sites to mirror their Motif distribution 8) Happy Downloading! -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Motif is now Open Source 8)
I have a copy. However, the license is 'interesting' enough to read that I'm not sure it can be used inside the JDK distribution, so if someone can give me an explanation that I can understand that I'm legal to distribute the library as part of an application, please show me in terms a mere engineer can understand. I think that you no longer have to include Motif with the JDK. Just let the distribution of Motif come from freebsd.org , i.e., a port or a package. My take is that companies distributing FreeBSD or linux are free to distribute the source and binary for those "Open Source" operating systems. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Motif is now Open Source 8)
I have a copy. However, the license is 'interesting' enough to read that I'm not sure it can be used inside the JDK distribution, so if someone can give me an explanation that I can understand that I'm legal to distribute the library as part of an application, please show me in terms a mere engineer can understand. I think that you no longer have to include Motif with the JDK. Just let the distribution of Motif come from freebsd.org , i.e., a port or a package. Too much hassle IMO. I'd *much* rather distribute it as part of the package, and I'm looking into how feasible it would be to distribute inside of the JDK. Well, just asked them because I don't see any problems in doing what you want because is for an Open Source Operating System. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/netgraph ng_parse.c ng_parse.h
Tnks for those interested in Archie's netgraph article see: http://www.daemonnews.org/23/netgraph.html -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/netgraph ng_parse.c ng_parse.h
Perhaps this could be of some use to some: http://java.sun.com/products/jtapi/jtapi-1.2/Overview.html Setting aside that is a java telephony system, jtapi deals with the aspect of an event driven system where the system can be described as a finite state machine. Why ? From a cursory look at netgraph it seems that it does not deal too well with exception events or events. A good book on this topic is: Essential JTAPI by Spencer Roberts which goes to great extent in describing services as well as architectures issues in implementing event driven systems. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/netgraph ng_parse.c ng_parse.h
Curious, do you have a write up on netgraph? Tnks -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new C++ compiler changes
rename it libstdc++.so.1. Then you just have to modify your executable so that it looks for libstdc++.so.1 instead of libstdc++.so.3 Why not just reinstall the problematic executables? Yeap, we do that quite often in Linux 8) Cheers -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please help spread the CVSup mirror load more evenly
There are couple of RFCs on network load balancing with respect to servers or services and I am sure that there are also widely available research papers. Most of those concentrate on balancing the load on the server itself. How about balancing the load on the network paths, I doubt very much that we have a server load problem near as much as we have a network load problem due to people not having ready access to the data that says ``this server is closest network wise to me''. Hi Rod! Perhaps RFC 2391 may be of use. Network Working Group P. Srisuresh Request for Comments: 2391 Lucent Technologies Category: Informational D. Gan Juniper Networks, Inc. August 1998 Load Sharing using IP Network Address Translation (LSNAT) Enjoy -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: rtld-elf, java + tya
I am fairly certain that Java + TYA worked before Jan 7 -- haven't upgraded my system since then. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please help spread the CVSup mirror load more evenly
If the user does specifiy a cvsup , can you decide for the user which server is best based upon some simple statistic? -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please help spread the CVSup mirror load more evenly
So have the cvsup client do the pinging to the server and extract its current work load or other vital statistic. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please help spread the CVSup mirror load more evenly
My only point is that the first response to a problem isn't to necessarily pull out emacs and start hacking away on code. Yea, it is easier to do in a regular zone file then to implement the network measurement logic into cvsup. Yes, it is a rather cool idea to rotate on the cvs servers without respect to latency, work load or rate of service response from the server. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please help spread the CVSup mirror load more evenly
Hi David, John can implement a ping echo packet protocol for cvsup whose response can have "cool" information on the server. Steven's book on Networking already has the code for doing network latency calculations . It is more like if John has the time to implement such scheme -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Neat little DPT utils...
On Wed, 19 Jan 2000, you wrote: Unfortunately, we currently have a regression problem in FreeBSD. Newer releases tend to drop support for things that have no active maintainer (or a maintainer who is too worn out by continually rewriting his or her software to cope with changed interfaces). Another unfortunate side effect of this is that some developers base their work on older releases rather than chase the moving target of -current. If thats the case, then FreeBSD should stop changing :). Rather, with the capabilities of NewBus and the module system could it not be organized in such a way that the interface the driver requires is loaded along with the driver itself? Perhaps older interfaces just call the functions of the new interfaces. Give them a 1 or 2 year grace period to convert over before dropping them cold. (Thats 1 year in -stable, and 1 year of -current). My strategy in the past has been to develop kernel stuff for -current . The interfaces to device drivers or modules is usually a very tiny part of the driver or module. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot messages for pci devices...
fxp0: Intel EtherExpress Pro 10/100B Ethernet port 0xc400-0xc43f mem 0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0 Is this level of verbosity really helping anybody ? I thought we printed out the port/mem stuff for ISA because it is usually jumpered by the admin, but for dynamic allocation busses/devices I think this should be "bootverbose" material. Or maybe we should always make the resource allocations bootverbose stuff now ? I think that the pci info should be displayed onlly in verbose mode . Some of the pci devices specially the newer graphic cards have tons of memory map registers and it is of virtually no use to users. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0 code freeze scheduled for Jan 15th
Curious , what is elischer.org ? 8) -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0 code freeze scheduled for Jan 15th
In some email I received from Matthew Dillon, sie wrote: [...] We are not going to repeat the 3.0 mess. IPV6 and IPSEC are important, but not important enough to delay the already-delayed 4.0 release. 4.1 is not too late for these babies. [...] Well, let me put it this way. 4.0-RELEASE sounds like it will start becoming available at about the same time as other OS's make new releases *with* IPv6/IPSec. You work it out whether or not FreeBSD will win or lose from those two being there or not there. For the short term the impact will be nill , zero , nada... Is not like companies get hold of a new technology and instantly start deploying it -- it will take some time ;specially, nowdays after a lot of companies are getting somewhat of a relief from Y2K work or scare With respect to FreeBSD people can always get an upgrade or cvsup . They want more ? Talk to JKH I am sure is willing to strike a sweet deal 8) -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Your misleading, no, LYING message to me
I have to say that PHK has become the MASTER at pissing people off, ensuring that his opponent goes the deep end and staying calm so the blame obviously does not fall on him. Got to admit his formula is very very nice 8) By a long shot the problem is NOT Karl. It takes at least TWO to engage in a combatitive conflict -- that is if you are not schizophreniac. The proper tactic to resolve the conflict should have been to wait a cool off period and then slug it off technically. Nevertheless, instead of waiting for Karl to cool off and attempt to ration with him , it was much easier to drive him further down: hence thru censorship the "technical" argument was won with virtually no technical effort at all -- Like I said earlier very very nice tactic ! -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Your misleading, no, LYING message to me
Hi David, My post is not really based upon the last Karl vs. Pohl thread. It is more on what I have observed quietly over the last few months . If the behavior is left unchecked you can rest assure that their will be more flares up. Again, to have waited for Karl to cool off is not that unreasonable to ask if the interested party wanted to reason with him. I supposed that there are some who are a virtuoso at calming and reasoning with extremely angry people. I have always opted to wait for the person to calm down and then try to reason with them. Perhaps , in this new WWW world my ways are wrong and old fashioned... Take Care Guys, I am back to hacking and yes I am having a great time ! -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc compile error
"David O'Brien" wrote:
On Wed, Dec 29, 1999 at 11:37:18AM -0800, Amancio Hasty wrote:
This is the scoop.
..snip..
gcc -v
Using builtin specs.
gcc version 2.95.2 19991024 (release)
..snip..
Without -O or -O2 the program compiles okay.
What other platforms w/gcc 2.95 have you tried to build this X11 version
on? What other non-Linux platforms w/gcc 2.95 have you tried to build
this X11 version on? Do you have a problem if you download the official
GCC 2.95.2 release and build it the old GNU'fashion way? Does a purely
stock GCC 2.95 bomb on this?? If so, it is a GCC problem and the issue
should be raised with Cygnus.
Yes it is a gcc-2.95.2 bug. It's fixed in the 2.96 snapshot in
ports/lang/gcc-devel.
Yeap,
gcc-devel installed from the ports directory:
gcc -v
Reading specs from /usr/local/lib/gcc-lib/i386-portbld-freebsd4.0/2.96/specs
gcc version 2.96 19991110 (experimental)
{root} gcc -c -O2 bug.c
That is as Peter said the bug is fixed on the 2.96 snapshot and I am currently
rebuilding X on my other system will find out more when the build finishes in
about 1/2 hour.
Take Care
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
gcc 2.96 snapshot and X
Last nite , I managed to compile all of XFree86 3.9.17 with no compiler bugs from gcc. /usr/local/bin/gcc -v Reading specs from /usr/local/lib/gcc-lib/i386-portbld-freebsd4.0/2.96/specs gcc version 2.96 19991110 (experimental) Enjoy -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc compile error
Sending out an attachment of that size to a public mailing list was
hardly necessary, and the increasing stridency of your posts leading
up to this only serve to indicate that you may be heading in the truly
wrong direction with all this and seriously need to rethink your
strategy before you do something that has people howling for your
blood.
- Jordan
Okay folks,
This is the scoop.
For the benefit of those which don't have access to the latest XFree86 release you can
download the file from ftp://rah.star-gate.com/pub/bug.c
uname -a
FreeBSD x.star-gate.com 4.0-CURRENT FreeBSD 4.0-CURRENT #2: Mon Dec 27 13:55:25 PST
1999 [EMAIL PROTECTED]:/usr/src/sys/compile/MUADIB i386
gcc -v
Using builtin specs.
gcc version 2.95.2 19991024 (release)
gcc -c -O2 bug.c
xf86vmode.c: In function `ProcXF86VidModeGetMonitor':
xf86vmode.c:1320: Unable to generate reloads for:
(insn 300 298 302 (parallel[
(set (reg:SI 0 %eax)
(fix:SI (fix:SF (subreg:SF (reg:SI 0 %eax) 0
(clobber (mem:HI (plus:SI (reg:SI 6 %ebp)
(const_int -34 [0xffde])) 0))
(clobber (mem:HI (plus:SI (reg:SI 6 %ebp)
(const_int -36 [0xffdc])) 0))
(clobber (mem:SI (plus:SI (reg:SI 6 %ebp)
(const_int -40 [0xffd8])) 0))
(clobber (scratch:HI))
] ) 145 {fix_truncsfsi2+1} (insn_list 293 (nil))
(expr_list:REG_DEAD (reg:SI 0 %eax)
(expr_list:REG_UNUSED (scratch:HI)
(nil
--
Without -O or -O2 the program compiles okay.
gcc -c bug.c
According to Peter, the ports/lang/gcc-devel (the current snapshot) appears to
compile this program fine -- that is the compiler bug has been fixed.
So there appears to be two solutions to get around this problem:
1. compile without -O
or
2. installed the latest snapshot of gcc.
Take Care Guys
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
gcc compiler problem part deux
Forgot to post about this new feature of /usr/libexec/cpp :
1. Test file
foo.c
main() {
#ifdef __FreeBSD__
printf("hello\n");
#endif
}
1. old freebsd-current
2. gcc -v
Using builtin specs.
gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)
/usr/libexec/cpp foo.c
# 1 "foo.c"
main() {
printf("hello\n");
}
/usr/libexec/cpp has __FreeBSD_ defined --- and this is not
problem.
2. Now a very recent FreeBSD -current
gcc -v
Using builtin specs.
gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)
/usr/libexec/cpp foo.c
# 1 "foo.c"
main() {
}
Voila! the "printf " disappeared.
This behavior breaks the XFree86 3.9.17 build because the procedure
to build imake depends on /usr/libexec/cpp defining __FreeBSD__
I patched locally the imake build so just for FreeBSD it adds a
-D__FreeBSD__
I presumed that the latest /usr/libexec/cpp behavior is also going to
break other package. Again for me is not a problem because
after a few hours I managed to circumvent the new /usr/libexec/cpp
feature.
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: gcc compiler problem part deux
There are packages such as XFree86 which called directly the installed
cpp. Those packages which rely on the old behavior of /usr/libexec/cpp
for instance defining __FreeBSD__ are now broken .
This was discussed weeks ago, and the new behaviour is correct. You
should be using 'cc -E' instead.
Forgot to post about this new feature of /usr/libexec/cpp :
1. Test file
foo.c
main() {
#ifdef __FreeBSD__
printf("hello\n");
#endif
}
1. old freebsd-current
2. gcc -v
Using builtin specs.
gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)
/usr/libexec/cpp foo.c
# 1 "foo.c"
main() {
printf("hello\n");
}
/usr/libexec/cpp has __FreeBSD_ defined --- and this is not
problem.
2. Now a very recent FreeBSD -current
gcc -v
Using builtin specs.
gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)
/usr/libexec/cpp foo.c
# 1 "foo.c"
main() {
}
Voila! the "printf " disappeared.
This behavior breaks the XFree86 3.9.17 build because the procedure
to build imake depends on /usr/libexec/cpp defining __FreeBSD__
I patched locally the imake build so just for FreeBSD it adds a
-D__FreeBSD__
I presumed that the latest /usr/libexec/cpp behavior is also going to
break other package. Again for me is not a problem because
after a few hours I managed to circumvent the new /usr/libexec/cpp
feature.
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: gcc compile error
Hi, We just have a buggy version of gcc and it appears that the register allocator is the main problematic area. This is not really a problem for me because what I first try out is a newer version of gcc if I can not get around the compile problem. At any rate remember that at least my reported compiler bug appears to be fixed in the latest gcc-devel port. On Wed, 29 Dec 1999, Amancio Hasty wrote: ! !Without -O or -O2 the program compiles okay. ! !gcc -c bug.c ! Ouch! This looks an awful lot like the last report with `GCC' and `problem' in the subject. As Matt just mentionned one or two posts ago, and as I observed in the last thread, have you tried making some of the variables `volatile?' Assuming of course that the code does compile well without the optimization flags, one would assume that the "problem" occurs because of caching of certain variable values in registers (not that this should be a problem, mind you; one would assume that the optimization isn't performed too well). Due to lack of time, and generally speaking, lack of experience with GCC, I haven't taken a detailed shot at debugging this. Bosko. -- Bosko Milekic Email: [EMAIL PROTECTED] WWW:http://pages.infinit.net/bmilekic/ -- -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc compiler problem part deux
It is more of a question of whether the packages for FreeBSD expect /usr/libexec/cpp to define __FreeBSD__ and in my case XFree86. Once I managed to find out what was wrong it was indeed easy for me to fix. If the "other" applications managed to compile correctly on FreeBSD because of /usr/libexec/cpp then I don't consider them to be broken. There are packages such as XFree86 which called directly the installed cpp. Those packages which rely on the old behavior of /usr/libexec/cpp for instance defining __FreeBSD__ are now broken . XFree86 is trivial to patch, since it already supports this behaviour (see our port), and other applications that expect cpp to define platform-specific symbols have always been broken. This was discussed weeks ago, and the new behaviour is correct. You should be using 'cc -E' instead. Forgot to post about this new feature of /usr/libexec/cpp : -- \\ 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] -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc compiler problem part deux
The usage came about oh about 8 years ago with the very first port of X to 386bsd by yours truly 8) Don't forget I did fix the problem on my X build and I am running the latest XFree86 3.9.xx on my other box. Take Care Forgot to post about this new feature of /usr/libexec/cpp : NO ONE should have ever have been using /usr/libexec/cpp directly. I have no idea where this usage came from. /usr/bin/cpp should have been used. 2. Now a very recent FreeBSD -current gcc -v Using builtin specs. gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release) Yes this is very well known, and has been discussed on both Ports and Current several times. A new /usr/bin/ccp is in the works that is a real binary and not the shell script we have today. *IF* world had been buildable today, we would probably have a new /usr/bin/cpp that does everything you want it to. This behavior breaks the XFree86 3.9.17 build because the procedure to build imake depends on /usr/libexec/cpp defining __FreeBSD__ So use ``cc -E'' instead. Simple. -- -- David([EMAIL PROTECTED]) -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc compile error
3. Raise this issue with Cygnus. Not really Cygnus is the wrong organization to raise this issue . As someone else pointed out the gcc-devel port does not exhibit the bug which I posted. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc compile error
Gcc 2.96 will not be out before 4.0. So Gcc 2.95.x is what is going into 4.0. Now should a Gcc 2.95.3 were to come out, then we'd get a new compiler for 4.0. Lets think about this in FreeBSD terms -- 4.0 does not have some problem that 3.4-R does. However it wasn't known that 3.4-R had this problem and Hi, I am running FreeBSD -current and I got no clue as to what is going on FreeBSD 3.xxx. The problem was reported for FreeBSD -current. Okay, lets hope that gcc 2.9.53 comes out before the release of FreeBSD 4.0. Take Care -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc compile error
Hi David, Last time, the problem does not exist with the gcc-devel port which directly implies that the problem has been fixed so I see no point on reporting the bug to Cygnus. I can in the future report the bug to Cygnus if the bug has not been fixed in a subsequent snapshot. I will play with gcc-devel some tonite to see if I can use it for all my ports. Some background: I am working on XFree86 to help bring about yuv + scaling hardware support -- my main priority is X for I if get too side tracked I may miss my window of opportunity to hack . Take Care -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc compile error
Thats nice . Now we have a compiler which fails to build X. Actually, that's one of the newest versions of gcc. Perhaps a later snapshot of gcc will work . GCC 2.95.2 is a *RELEASED* version. We don't use snapshots as the base compiler. What every the problem is 4.0 will live with it unless someone narrows down the problem more. -- -- David([EMAIL PROTECTED]) -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc compile error
Yes, I can rightfully claim that you cannot build XFree86 3.9 xxx dated December 24 with the default gcc compiler on FreeBSD -current. I am running FreeBSD -current and XFree86 3.9xxx current. Thats nice . Now we have a compiler which fails to build X. This seems like hyperbole. I'm able to build X just fine with the -current compiler, so to directly imply that we can't do so flies in the face of common sense and experience. - Jordan -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc compile error
The details were previously posted by . Good Nite -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc compile error
On Tue, 28 Dec 1999, Amancio Hasty wrote:
The details were previously posted by .
Good Nite
Whatever ate the details on your previous post seems to be at it again.
Here is a copy of my mail post which I received from the -current mail list
that is my post went out intact.
Posted on Sat, 25 Dec 1999 23:17:45 -0800
---
While trying to compile the latest version of XFree86 I found the following
compiler bug.
{root} gcc -v
Using builtin specs.
gcc version 2.95.2 19991024 (release)
I assume that this an old version of gcc...
xc/programs/Xserver/Xext
cc -c -pipe -O2 -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -Wstrict-prototypes
-Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wnested-externs -I.
-I../include -I../../../exports/include/X11 -I../../../include/extensions
-I../../../include/fonts -I../mi -I../../../programs/Xserver/hw/xfree86/common
-I../../../include/fonts -I../../.. -I../../../exports/include -DCSRG_BASED -DSHAPE
-DXINPUT -DXKB -DLBX -DXAPPGROUP -DXCSECURITY -DTOGCUP -DXF86BIGFONT -DDPMSExtension
-DPIXPRIV -DPANORAMIX -DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH
-DXFreeXDGA -DXvExtension -DXFree86LOADER -DXFree86Server -DXF86VIDMODE
-DX_BYTE_ORDER=X_LITTLE_ENDIAN -DSMART_SCHEDULE -DNDEBUG -DFUNCPROTO=15
-DNARROWPROTO xf86vmode.c
In file included from xf86vmode.c:41:
../include/extnsionst.h:91: warning: function declaration isn't a prototype
../include/extnsionst.h:100: warning: function declaration isn't a prototype
../include/extnsionst.h:106: warning: function declaration isn't a prototype
xf86vmode.c: In function `ProcXF86VidModeGetMonitor':
xf86vmode.c:1320: Unable to generate reloads for:
(insn 300 298 302 (parallel[
(set (reg:SI 0 %eax)
(fix:SI (fix:SF (subreg:SF (reg:SI 0 %eax) 0
(clobber (mem:HI (plus:SI (reg:SI 6 %ebp)
(const_int -34 [0xffde])) 0))
(clobber (mem:HI (plus:SI (reg:SI 6 %ebp)
(const_int -36 [0xffdc])) 0))
(clobber (mem:SI (plus:SI (reg:SI 6 %ebp)
(const_int -40 [0xffd8])) 0))
(clobber (scratch:HI))
] ) 145 {fix_truncsfsi2+1} (insn_list 293 (nil))
(expr_list:REG_DEAD (reg:SI 0 %eax)
(expr_list:REG_UNUSED (scratch:HI)
(nil
*** Error code 1
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: gcc compile error
Look I stated previously and only a few hours ago:
---
Yes, I can rightfully claim that you cannot build XFree86 3.9 xxx dated
December 24 with the default gcc compiler on FreeBSD -current.
I am running FreeBSD -current and XFree86 3.9xxx current.
---
More precisely :
FreeBSD -current was last cvsup on my system on Dec 23 18:59.
XFree86 3.9.xxx was cvsup on December 24th I am sorry but this is
sufficient information to reproduce the problem.
Amancio Hasty wrote:
On Tue, 28 Dec 1999, Amancio Hasty wrote:
The details were previously posted by .
Good Nite
Whatever ate the details on your previous post seems to be at it again.
Here is a copy of my mail post which I received from the -current mail list
that is my post went out intact.
It isn't much use to anyone like this... We need to be able to reproduce
this. What release of xfree86 is this? 3.9.16 as released? if not you will
need to give us code if you want help.
Failing that, how about a cc -E of the file in question so we can compile it
standalone and see what is going wrong with the inline asm?
Posted on Sat, 25 Dec 1999 23:17:45 -0800
---
While trying to compile the latest version of XFree86 I found the following
compiler bug.
{root} gcc -v
Using builtin specs.
gcc version 2.95.2 19991024 (release)
I assume that this an old version of gcc...
xc/programs/Xserver/Xext
cc -c -pipe -O2 -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -Wstrict-pr
ototypes -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wne
sted-externs -I.
-I../include -I../../../exports/include/X11 -I../../../include/extensions
-I../../../include/fonts -I../mi -I../../../programs/Xserver/hw/xfree86/
common
-I../../../include/fonts -I../../.. -I../../../exports/include -DCSRG_BASED
-DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP -DXCSECURITY -DTOGCUP -DXF86BIGF
ONT -DDPMSExtension
-DPIXPRIV -DPANORAMIX -DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH
-DXFreeXDGA -DXvExtension -DXFree86LOADER -DXFree86Server -DXF86VIDMODE
-DX_BYTE_ORDER=X_LITTLE_ENDIAN -DSMART_SCHEDULE -DNDEBUG -DFUNCPROTO=15 -DN
ARROWPROTO xf86vmode.c
In file included from xf86vmode.c:41:
../include/extnsionst.h:91: warning: function declaration isn't a prototype
../include/extnsionst.h:100: warning: function declaration isn't a prototype
../include/extnsionst.h:106: warning: function declaration isn't a prototype
xf86vmode.c: In function `ProcXF86VidModeGetMonitor':
xf86vmode.c:1320: Unable to generate reloads for:
(insn 300 298 302 (parallel[
(set (reg:SI 0 %eax)
(fix:SI (fix:SF (subreg:SF (reg:SI 0 %eax) 0
(clobber (mem:HI (plus:SI (reg:SI 6 %ebp)
(const_int -34 [0xffde])) 0))
(clobber (mem:HI (plus:SI (reg:SI 6 %ebp)
(const_int -36 [0xffdc])) 0))
(clobber (mem:SI (plus:SI (reg:SI 6 %ebp)
(const_int -40 [0xffd8])) 0))
(clobber (scratch:HI))
] ) 145 {fix_truncsfsi2+1} (insn_list 293 (nil))
(expr_list:REG_DEAD (reg:SI 0 %eax)
(expr_list:REG_UNUSED (scratch:HI)
(nil
*** Error code 1
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: gcc compile error
Actually, that's one of the newest versions of gcc. Perhaps a later snapshot of gcc will work . attached make.log. There's something about not allowing access to the cx register. I am not into hacking gcc's register allocator 8) -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
gcc compile error
While trying to compile the latest version of XFree86 I found the following
compiler bug.
{root} gcc -v
Using builtin specs.
gcc version 2.95.2 19991024 (release)
I assume that this an old version of gcc...
xc/programs/Xserver/Xext
cc -c -pipe -O2 -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -Wstrict-prototypes
-Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wnested-externs -I.
-I../include -I../../../exports/include/X11 -I../../../include/extensions
-I../../../include/fonts -I../mi -I../../../programs/Xserver/hw/xfree86/common
-I../../../include/fonts -I../../.. -I../../../exports/include -DCSRG_BASED -DSHAPE
-DXINPUT -DXKB -DLBX -DXAPPGROUP -DXCSECURITY -DTOGCUP -DXF86BIGFONT -DDPMSExtension
-DPIXPRIV -DPANORAMIX -DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH
-DXFreeXDGA -DXvExtension -DXFree86LOADER -DXFree86Server -DXF86VIDMODE
-DX_BYTE_ORDER=X_LITTLE_ENDIAN -DSMART_SCHEDULE -DNDEBUG -DFUNCPROTO=15
-DNARROWPROTO xf86vmode.c
In file included from xf86vmode.c:41:
../include/extnsionst.h:91: warning: function declaration isn't a prototype
../include/extnsionst.h:100: warning: function declaration isn't a prototype
../include/extnsionst.h:106: warning: function declaration isn't a prototype
xf86vmode.c: In function `ProcXF86VidModeGetMonitor':
xf86vmode.c:1320: Unable to generate reloads for:
(insn 300 298 302 (parallel[
(set (reg:SI 0 %eax)
(fix:SI (fix:SF (subreg:SF (reg:SI 0 %eax) 0
(clobber (mem:HI (plus:SI (reg:SI 6 %ebp)
(const_int -34 [0xffde])) 0))
(clobber (mem:HI (plus:SI (reg:SI 6 %ebp)
(const_int -36 [0xffdc])) 0))
(clobber (mem:SI (plus:SI (reg:SI 6 %ebp)
(const_int -40 [0xffd8])) 0))
(clobber (scratch:HI))
] ) 145 {fix_truncsfsi2+1} (insn_list 293 (nil))
(expr_list:REG_DEAD (reg:SI 0 %eax)
(expr_list:REG_UNUSED (scratch:HI)
(nil
*** Error code 1
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: New sound driver and Linux games
It could be that the OSS Voxware driver does something "unintentional" that some programmers are relying on. Unreal Tournament and XMAME audio works fine under newpcm, for instance. Strange. Not really . Just go to http://www.opensound.com and look at their api in addition you have the old voxware sound driver in the kernel to look at . I made Quake and Quake 2 work with the voxware sound driver and it was not that hard . -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
3. Get pissed off with FreeBSD and go elsewhere. don't worry I am sure that quite a few user have left already. This kind of situation reminds of when I accidently broke the gus max backwards compatibility. An old friend of mine sent me a quiet note stating that he switch OSes cause he couldn't use his soundcard with FreeBSD . The mail didn't surprise me what really surprise is that he just switch OSes without warning me. So we have quiet types and "loud" types of users. The users which complaint don't bother me at least I know what they are thinking . The users / developers ratio initially bother me in the multimedia mailing list;however, I came to the conclusion that we do need a large user base to maximize test coverage and feasibility . -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Flash (was: Re: Sound card support)
Hi .. Under current the flash plugin works with the linux version of Netscape and the linuxelator ... Sound etc, everything works ok ... except for the odd crash of netscape which is normal :) Hmmm. The developers of mozilla are dying to get bug reports http://www.mozilla.org 8) Someone for berkeley.edu last week reported 36 bugs which made the developers very happy ... -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
The sound drivers are fine . What we need are people willing to work on the sound drivers . -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SB Live! driver
Hi, Take it up with -multimedia . The gus tarted to talk about it over there. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SB Live! driver
Subscribe to : [EMAIL PROTECTED] Have Fun Amancio -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
vga driver and signal
Say is there anyone that can add signal delivery to the /sys/dev/fb/vga.c? (For now any quick hack to the driver for delivering the signal will do ) The context is from a posting to the xfree86 mailing list: [EMAIL PROTECTED] said: You need to fit one event in per retrace. If you knew the phase of the sampling clock with respect to the retrace you could do that by skipping one sample then two then one, etc... But we don't know the phase and if you do that with arbitrary phase you end up sending two events in one retrace and then skipping the next and it looks worse. If we had a signal delivered at vertical retrace time, we could easily sync the mouse rate with the video rate -- run the mouse events through a simple filter and estimate mouse position at the vertical retrace interval using some forward estimation. Additionally, the vertical retrace signal could be used for the double buffering extension to avoid tearing, and for the sync extension which kinda wants this. And for many video cards which can't update colormaps or cursor positions at other times without visible artifacts on the screen. It would take some kernel work though; the results might well be worth the effort. -keith I am too busy nowdays working :( Have Fun Guys! -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Discussions starting on -arch.
I am not that really interested on threads.. Is there a possibility of having an async call gate for which the kernel can do the scheduling whether be for a uni processor or a multi processor enviroment. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Timeframe on XFree86 signal fix
Hi folks, A sequence of silly mistakes and circumstances have conspired against me to make it impossible for me to run XFree86. I understand that the XFree86 build is broken in the face of recent signal-related changes. I want to know how long I can expect to wait for XFree86 to build on CURRENT again. I'm not pushing, I just want to know whether I'm in for a wait of less than a week (in which case I'll do without XFree86) or whether I can expect to wait longer (in which case I'll bite the bullet and undo my silly mistakes). I too was pressed for time and what I did was to dig up the source for a program which uses signals and cut paste the include files to FSConServ.c . I played a little with gcc -E which displays the processing of the include files and took a brief look at signa.h and saw the check for _P1003_1B_VISIBLE... This is all academic since the proper fix was posted to the list. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
3dfx Driver?
Has anyone ported the linux 3DFx Driver to FreeBSD? Tnks! -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3dfx Driver?
Don't have much time now days to volunteer due to work overload. If I get a chance one of these nights I will port it. My focus is to provide decent X video support appropiate for h.261 , h.263 , and mpeg -- which basically entails yuv + scaling hardware assist. In other words 3dfx is a secondary issue. Cheers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
May 99 Snapshot and -current
Got a new disk and I am trying to upgrade from the May 1999 snapshot to today's current. I recompiled the kernel , install it and reboot afterwards the boot loader fails to load the new kernel so should I upgrade my boot blocks with the latest sources? Tnks -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: sigset_t changes committed
Without proper linux support we are dead . Now I have to get off my soap box and let the work continue 8) Best Regards -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Loss of Functionality with newpnp
It requires converting the ancient voxware driver to newbus which isn't really feasable. I am not sure about that ... The irq handling, card registration on the voxware is fairly straight forward. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ccd build failure
Stay nice 8) Never give the opposition an opportunity to get the best of you for most likely they will fully exploit your weakness . After all isn't that was opposition is all about? -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Communicator 4 and LDAP
click on "Communicator" - AddressBook , then on your ldap server: Fill in : Description: User Friendly name for your ldap server LDAP Server: ldap's hostname Server Root: your server root Port Number : the port number where your ldap server is listening to From the address book window you should be able to query the ldap server. Cheers -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Communicator 4 and LDAP
Hi, I can't connect to the default ldap servers;however, on my win98 box I can connect to the InfoSpace ldap server. I have a local ldap server here and I can connect to it using netscape with no problem. Try it : rah.star-gate.com port 389 -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Clean Build!
Last nite around 1am or so I cvsup my system and managed to build the world and the kernel 8) Not sure how stable is -current so far in a uni processor configuration the system seems to be okay. Enjoy -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: evil -current
Don't know -current is working fine for me over here as well as the latest XFree86 snapshot. It does help if you post further details like system configuration: uni processor vs smp , scsi vs ide , etc... Cheers -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Mucho Bandwith
The claim of this arcticle is that the researchers are at a lost of what to do with their CA*Net3 network (80 giga bits /second ). http://abcnews.go.com/sections/tech/CuttingEdge/canadanet990827.html Hmmm... I wonder what would happen if ftp.freebsd.org was moved to CA*Net3 8) I am sure that some on the list can figure out other creative uses like clustering. Enjoy -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Softupdates reliability?
PIII 450Mhz are going for about $175 see http://www.pricewatch.com . Heck , at that price get two 8) Enjoy -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [re]writable cdrom drive
Amancio Hasty wrote... Amancio Hasty wrote... I have to agree with Matt on this plus the set of defaults is system wide . What are you agreeing with him on? Why not quote what you're talking about? Is it possible to get a system bus enumeration from the system so a program such a cdrecord can attempt to make an intelligent decision as to which device is the cd recorder for instance we know that the system can print the device's name and its scsi address: If you want a bus number, there's a really easy way to get it: # camcontrol devlist EXABYTE EXB-10i 2.6 at scbus0 target 3 lun 0 (pass0,ch0) EXABYTE EXB-8500-85Qanx0 0415at scbus0 target 4 lun 0 (pass1,sa0) SEAGATE ST31230W 0510at scbus1 target 0 lun 0 (pass2,da0) SEAGATE ST32155N 0318at scbus1 target 1 lun 0 (pass3,da1) PLEXTOR CD-R PX-R412C 1.04 at scbus1 target 3 lun 0 (pass4,cd0) PLEXTOR CD-ROM PX-4XCS 1.04 at scbus1 target 6 lun 0 (pass5,cd1) SEAGATE ST34371N 0484at scbus2 target 0 lun 0 (pass6,da2) So, in this case, the bus,target,lun combination for my CD-R is 1,3,0. cdrecord itself also has a slightly more obtuse way of doing the same thing: # cdrecord -scanbus Cdrecord release 1.8a22 Copyright (C) 1995-1999 J_rg Schilling scsibus0: 0) * 1) * [ ... ] The camcontrol output is easier to figure out, though. Ken This is about ease of use . cdrecord in the absence of a device specification should query the bus and present the user with a choice of cd recorder devices ideally if there is one cd recorder it should go ahead an use it if such behavior is not desired then create an option "--confirm" to ask the user if its okay to use the "guessed" cd recorder. If you think cdrecord should do something different, talk to Joerg Schilling [EMAIL PROTECTED] about it. camcontrol is a generic scsi command line interface and very nice . What I am after is a generic bus enumerator API so apps like cd recorder or fxtv can use to locate the device in the absence of a specified device. There is a generic SCSI bus enumerator API, and one for PCI as well. There isn't a generic API to get trees of devices of any type in the system, though. With new-bus that might be possible, but having done two enumerator APIs already (I wrote the CAM and PCI enumerator code), I can predict that it might be very complicated to do properly. (Things get really hairy when you have to keep the device tree from changing while you're traversing it.) In any case, for the two applications you specified, cdrecord is only interested in SCSI devices, and there is already an API -- that cdrecord already supports -- to do bus/device enumeration. The cdrecord -scanbus code already uses that API. Similarly, there is already a PCI device listing interface, so fxtv should be able to easily pull out the devices it is interested in. All it has to do is search for all "meteor" or "bktr" devices to find what it wants. Ken Now how can I map a device name from this bus enumeration so that I can issue an "open" to the device: pciconf -l chip0@pci0:0:0: class=0x06 card=0x chip=0x12378086 rev=0x02 hdr=0x00 isab0@pci0:1:0: class=0x060100 card=0x chip=0x70008086 rev=0x01 hdr=0x00 ide_pci0@pci0:1:1: class=0x010180 card=0x chip=0x70108086 rev=0x00 hdr=0x00 chip1@pci0:1:2: class=0x0c0300 card=0x chip=0x70208086 rev=0x01 hdr=0x00 de0@pci0:9:0: class=0x02 card=0x11001385 chip=0x00091011 rev=0x22 hdr=0x00 bktr0@pci0:10:0:class=0x04 card=0x13eb0070 chip=0x036e109e rev=0x02 hdr=0x00 none0@pci0:10:1:class=0x048000 card=0x13eb0070 chip=0x0878109e rev=0x02 hdr=0x00 ahc0@pci0:11:0: class=0x01 card=0x chip=0x81789004 rev=0x00 hdr=0x00 ahc1@pci0:12:0: class=0x01 card=0x chip=0x71789004 rev=0x03 hdr=0x00 vga-pci0@pci0:13:0: class=0x03 card=0x0000 chip=0x0519102b rev=0x01 hdr=0x00 -- Amancio Hasty [EMAIL PROTECTED] 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: [re]writable cdrom drive
Amancio Hasty wrote...
There is a generic SCSI bus enumerator API, and one for PCI as well. There
isn't a generic API to get trees of devices of any type in the system,
though. With new-bus that might be possible, but having done two
enumerator APIs already (I wrote the CAM and PCI enumerator code), I can
predict that it might be very complicated to do properly. (Things get
really hairy when you have to keep the device tree from changing while
you're traversing it.)
In any case, for the two applications you specified, cdrecord is only
interested in SCSI devices, and there is already an API -- that cdrecord
already supports -- to do bus/device enumeration. The cdrecord -scanbus
code already uses that API.
Similarly, there is already a PCI device listing interface, so fxtv should
be able to easily pull out the devices it is interested in. All it has to
do is search for all "meteor" or "bktr" devices to find what it wants.
Ken
Now how can I map a device name from this bus enumeration so that I can issue
an "open" to the device:
pciconf -l
chip0@pci0:0:0: class=0x06 card=0x chip=0x12378086 rev=0x02
hdr=0x00
isab0@pci0:1:0: class=0x060100 card=0x chip=0x70008086 rev=0x01
hdr=0x00
ide_pci0@pci0:1:1: class=0x010180 card=0x chip=0x70108086
rev=0x00 hdr=0x00
chip1@pci0:1:2: class=0x0c0300 card=0x chip=0x70208086 rev=0x01
hdr=0x00
de0@pci0:9:0: class=0x02 card=0x11001385 chip=0x00091011 rev=0x22
hdr=0x00
bktr0@pci0:10:0:class=0x04 card=0x13eb0070 chip=0x036e109e
rev=0x02 hdr=0x00
none0@pci0:10:1:class=0x048000 card=0x13eb0070 chip=0x0878109e
rev=0x02 hdr=0x00
ahc0@pci0:11:0: class=0x01 card=0x chip=0x81789004 rev=0x00
hdr=0x00
ahc1@pci0:12:0: class=0x01 card=0x chip=0x71789004 rev=0x03
hdr=0x00
vga-pci0@pci0:13:0: class=0x03 card=0x chip=0x0519102b
rev=0x01 hdr=0x00
Only one of the above devices actually has a character device interface in
/dev. All you have to do is something like this:
sprintf(foo, "/dev/%s%d", p-pd_name, p-pd_unit);
The only way it would become complicated is if the device name in the
kernel were different than the device name in /dev.
Ken
Or if there is a system call or modification to open such that I can issue :
open("pci0:10:0", .)
On the kernel side, I hope that the pci code can translate a bus enumeration
to an actual major , minor device.
The only problem that I see with such an approach is security and I would
rather deal with that later.
--
Amancio Hasty
[EMAIL PROTECTED]
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: [fwd] [fm/news] newsletter for Aug 18th 1999, 23:59
Hi Linux land does not look so pretty now days ... Playing with Sun's java jre on linux. Ran jre libgc on redhat 6.0 no problem. slackware 4.0 appears to only like jre libc Suse 6.1 does not like either jre libc nore jre libgc. So on My customer should ship an entire linux box with their product 8) Be Happy -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: How To Burn CDs
If you have the physical memory sure however if you don't then you will start swapping and most likely your cd recording will fail. Hence my recommendation for a small size buffer. And to the list. Please keep the comments or suggestions rolling and hopefully by early next we will have a nice "How To Burn CD " document. Cheers "Another possibility, if you have the RAM, is to use the team(1) program (it's in the ports) to buffer the data as it goes to the burner. Any reason not to use ``cdrecord -fs=64m'' (or some simular size) -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: How To Burn CDs
If you don't have the time to trim, we don't have the time to read your Easy , Easy we are coming along fine so far so please keep the flame temperature down. If you are compelled or annoyed at the poster send him private e-mail and possibly a pointer to net - etiguette. If you do it nicely you may actually make a long term friend ... Cheers -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: How To Burn CDs
Then there is no advantage in using `team' vs. ``cdrecord -fs=XX'', right? -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) As far as I can tell there is no difference other one component less to use and ease of use. Cheers -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: How To Burn CDs
"Another possibility, if you have the RAM, is to use the team(1) program (it's in the ports) to buffer the data as it goes to the burner. Any reason not to use ``cdrecord -fs=64m'' (or some simular size) Any reason to? I mean, I never had to go over the default cdrecord uses. Since the author was already suggesting the use of team(1) he obvisiously wants a larger buffer. I was mearly asking if there was something about team(1) better than ``cdrecord -fs=XX''. To me in the context of cdrecord, cdrecord's option "fs" and team are about the same. Perhaps someone more familiar with cdrecord fifo.c's circular buffer algorithm and team can express a different opinion. Cheers -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: user friendly creation of CDs (was: Re: patches for tosha?)
Hi, In my case is a lot easier to customize a simple shell script and use it. Is just that gcombust comes from linux perhaps if I keep using I can get over my hurdle 8) Have Fun Guys! Heh. I see, you want a program that one could use without having to know _anything_. Your right thats not what gcombust is, but its still useful for those of us who know `something'... On Fri, Aug 20, 1999 at 05:02:07PM -0700, Amancio Hasty wrote: Yes, I tried gcombust and opted for the command line approach gcombust looks great ;however, I expect for user firiendly land less knobs for instance: burn iso 9660 cd Select files or directories type of CD : CD-R , CD-RW then pull the appropiate information for buffering and optimal speed from a database. Not sure a database would be enough for that, as these not only vary for each system (hardware) but also depend on . the type of files to be written (big ones or many small ones) and of course the performance of the disk/controller/fs their on (and the net if their not local) . current and near-future system load (for example any cronjobs coming up that will be hammering the source disk, or network?) (is that all?) of course you could reduce the problems by simply always creating an image file but then you can't write CDs once your low on free space. ... Sometimes being the hacker of the house is not an easy task 8) :) Still i'd like to know of any solution you come up with... Regards, -- Juergen Lock [EMAIL PROTECTED] (remove dot foo from address to reply) -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
How To Burn CDs
o use the team(1) program (it's in the ports) to buffer the data as it goes to the burner. You basically put it into the pipeline between mkisofs and cdrecord, and it buffers up to 5MB in memory (default, adjustable). Of course, you've got to have enough RAM to not go into swap during the operation. It's a very nice program, and I've been told that, with enough memory (32-64MB), you can be running X11 and compiling programs while the CD is burning (this is with a 2X burner, though)." "It should be noted that the 'cdrecord' program implements a FIFO itself, and you can specify the size. The default is 2MB. cdrecord uses a shared memory segment and forks so the process buffering the data is made independant of the buffer draining it. Modern CD writers usually have 1-2MB of buffer internally. The newer Yamahas, for example, have 2MB. So right off the bat we have around 4MB. Still, when you are writing at 600KB/sec it is possible to get behind if the filesystem you are building has lots of small files. Apart from writing the mkisofs output to a file, the easiest solution is to tell cdrecord to burn at a slower rate - e.g. 1x or 2x instead of 4x or 6x. Possible Problem and we need clarification And to head off another question: When you are recording to a CD-RW you can do a 'quick erase' of the media using 'cdrecord blank=fast'. This does not actually erase the data, so if you have used say 100MB you will only have 550MB left. You can actually erase the media using 'cdrecord blank=all', which takes a while. In my experience, this is not true. I have used blank=fast on a CDRW that has over 500 MB written, and then written another 500 MB without a problem. I have the same experience. Maybe someone into the physics of the media can explain what the pros-cons are as far as the media itself is concerned? Hardware : Yamaha CRW6416sz scsi 2 internal cd recorder I bought the Yamaha CRW6416sz scsi 2 iternal because it is somewhat cheap and reliable . You can buy one at CompUSA for $300. Reported scsi CD recorders which work and by no means this list is not exhaustive rather is nice to know from a FreeBSD user that it works on their boxes. 1. JKH swears by his Smart and Friendly Rocket Recorder scsi cd recorder 8) Honest is probably a good drive because JKH burns quite a few CDs. 2. Plextor scsi recorders 4x and 8x good recommendation from the list. 3. Philips CDD-3600 CDRW drive 4. Yamaha 4416 scsi recorder known to work on FreeBSD, Linux, SCO, HP/UX, and NT 5. Yamaha 6416sz scsi cd recorder. Hidetoshi Shimokawa [EMAIL PROTECTED] reported: I bought DVD-RAM drive for $400. 5.2GB(double side) media is around $35, you can use them as 2.3GB x 2 disks. Enabling raw-write in scsi_cd.c, you can newfs/mount DVD-RAM as UFS. Write speed is around 500KB/s, and read speed is around 1.4MB/s. Now this sounds like a very nice scsi cd recorder . Further input on DVD-RAM is welcome . -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: user friendly creation of CDs (was: Re: patches for tosha?)
Yes, I tried gcombust and opted for the command line approach gcombust looks great ;however, I expect for user firiendly land less knobs for instance: burn iso 9660 cd Select files or directories type of CD : CD-R , CD-RW then pull the appropiate information for buffering and optimal speed from a database. You need something special to burn your CD ? pull out the "expert" tab menus. If I showed gcombust to Bettina , she would snap you got to be kidding and I have to confess that she is right. She already ask me is the system ready for you and I had to respond sorry not quite there yet you will have to wait about a week and she responded thats not bad take your time . Sometimes being the hacker of the house is not an easy task 8) Cheers -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [re]writable cdrom drive
: you can do a 'quick erase' of the media using 'cdrecord blank=fast'. : This does not actually erase the data, so if you have used say 100MB : you will only have 550MB left. You can actually erase the media using : 'cdrecord blank=all', which takes a while. : :In my experience, this is not true. I have used blank=fast on a CDRW :that has over 500 MB written, and then written another 500 MB without :a problem. Really? I'll have to mess with it some more. Maybe I had tried to write more data then I thought in my last test. I just happen to be writing another cd 8) mkisofs -R /mount/cdrom | cdrecord -blank=fast -v fs=10m speed=3 - Track 01: 597 MB written (fifo 100%).Total extents actually written = 311018 Total translation table size: 0 Total rockridge attributes bytes: 1076001 Total directory bytes: 3112960 Path table size(bytes): 15778 Max brk space used 84a29c 311018 extents written (607 Mb) Track 01: 607 MB written (fifo 100%). Track 01: Total bytes read/written: 636964864/636964864 (311018 sectors). Writing time: 2190.437s Fixating... Fixating time: 129.090s cdrecord: fifo had 10034 puts and 10034 gets. cdrecord: fifo was 0 times empty and 9713 times full, min fill was 89%. This is like the third time that I writing pretty much the same image to the CD. Enjoy -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: patches for tosha?
As Amancio Hasty wrote ... Or does tosha work with CAM? It does for me... (3.2-stable). Hi, I think is that tosha does not know how to read audio tracks with my Yamaha cd recorder. The Yamaha have a slightly weird way of reading the audio tracks . I have cdda2wav as an example on how to read audio tracks on Yamaha CDs. The only gotcha is that is for linux so I will have to translate the linux scsi commands to CAM. Writing audio tracks is no problem with "cdrecord". Cheeers -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: patches for tosha?
Hi!
I am totally full of joy to be able to read audio CDs in FreeBSD .
pwd
/mnt/ports/sysutils/cdrecord/work/cdrecord-1.8/cdda2wav/OBJ/i386-freebsd-cc
{root} ./cdda2wav -D0,1,0 -B
266240 bytes buffer memory requested, 4 buffers, 27 sectors
Read TOC CD Text failed (probably not supported).
#Cdda2wav version schily0.4_freebsd_4.0-current_i386_i386 real time sched.
soundcard support
AUDIOtrack pre-emphasis copy-permitted tracktype channels
1-12 no no audio2
Table of Contents: total tracks:12, (total time 55:27.43)
1.( 4:37.09), 2.( 4:38.97), 3.( 5:17.63), 4.( 3:50.24), 5.( 4:11.23)
6.( 5:28.77), 7.( 4:40.96), 8.( 3:55.51), 9.( 4:57.36), 10.( 4:45.71)
11.( 3:40.87), 12.( 5:21.09),
Table of Contents: starting sectors
1.( 0), 2.( 20782), 3.( 41705), 4.( 65527), 5.( 82795)
6.( 101637), 7.( 126295), 8.( 147367), 9.( 165030), 10.( 187332)
11.( 208760), 12.( 225325), lead-out( 249407)
CDDB discid: 0xb80cfd0c
Tnks A Lot!
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: [re]writable cdrom drive
Please Matt "burn" a summary document ... (Gosh I have been burning too many CDs 8) ) -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: patches for tosha?
Hi, I am all set . cdrecord-1.8a22 includes cdda2wav as [EMAIL PROTECTED] pointed out and it does work with my Yamaha cd recorder . In summary using FreeBSD-current of about two weeks ago , I am now able to : 1. to burn iso 9660 with mkisofs + cdrecord 2. extract CD audio tracks with cdda2wav 3. Burn audio cds with cdrecord . No other external program is necessary to burn the Audio CD. A bit more work is needed to make the creation of CDs on FreeBSD user friendly and the responsibilty for that falls more on the authors of the CD tools. With FreeBSD-current as of this morning, [EMAIL PROTECTED] (Arno J. Klaassen just reported having problems with cdd2wav panicking the system with: launching cdda2wav immediately panics with: panic: setrunqueue: invalid rtprio type Cheers As Amancio Hasty wrote ... As Amancio Hasty wrote ... Or does tosha work with CAM? It does for me... (3.2-stable). To qualify that a bit more: it works on my Toshiba XM-5701TA (surprise..) and also on my Philips CDD-3600 CDRW drive. I think is that tosha does not know how to read audio tracks with my Yamaha cd recorder. The Yamaha have a slightly weird way of reading the audio tracks . I have cdda2wav as an example on how to read audio tracks on Yamaha CDs. The only gotcha is that is for linux so I will have to translate the linux scsi commands to CAM. Maybe a check on the xmcd source code is of interest. It has a number of vendor-unique support files with interesting info. Wilko -- | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [re]writable cdrom drive
Amancio Hasty wrote... I have to agree with Matt on this plus the set of defaults is system wide . What are you agreeing with him on? Why not quote what you're talking about? Is it possible to get a system bus enumeration from the system so a program such a cdrecord can attempt to make an intelligent decision as to which device is the cd recorder for instance we know that the system can print the device's name and its scsi address: If you want a bus number, there's a really easy way to get it: # camcontrol devlist EXABYTE EXB-10i 2.6 at scbus0 target 3 lun 0 (pass0,ch0) EXABYTE EXB-8500-85Qanx0 0415at scbus0 target 4 lun 0 (pass1,sa0) SEAGATE ST31230W 0510at scbus1 target 0 lun 0 (pass2,da0) SEAGATE ST32155N 0318at scbus1 target 1 lun 0 (pass3,da1) PLEXTOR CD-R PX-R412C 1.04 at scbus1 target 3 lun 0 (pass4,cd0) PLEXTOR CD-ROM PX-4XCS 1.04 at scbus1 target 6 lun 0 (pass5,cd1) SEAGATE ST34371N 0484at scbus2 target 0 lun 0 (pass6,da2) So, in this case, the bus,target,lun combination for my CD-R is 1,3,0. cdrecord itself also has a slightly more obtuse way of doing the same thing: # cdrecord -scanbus Cdrecord release 1.8a22 Copyright (C) 1995-1999 Jörg Schilling scsibus0: 0) * 1) * 2) * 3) 'EXABYTE ' 'EXB-10i ' '2.6 ' Removable Juke Box 4) 'EXABYTE ' 'EXB-8500-85Qanx0' '0415' Removable Tape 5) * 6) * 7) * scsibus1: 100) 'SEAGATE ' 'ST31230W' '0510' Disk 101) 'SEAGATE ' 'ST32155N' '0318' Disk 102) * 103) 'PLEXTOR ' 'CD-R PX-R412C ' '1.04' Removable CD-ROM 104) * 105) * 106) 'PLEXTOR ' 'CD-ROM PX-4XCS ' '1.04' Removable CD-ROM 107) * scsibus2: 200) 'SEAGATE ' 'ST34371N' '0484' Disk 201) * 202) * 203) * 204) * 205) * 206) * 207) * The camcontrol output is easier to figure out, though. Ken This is about ease of use . cdrecord in the absence of a device specification should query the bus and present the user with a choice of cd recorder devices ideally if there is one cd recorder it should go ahead an use it if such behavior is not desired then create an option "--confirm" to ask the user if its okay to use the "guessed" cd recorder. camcontrol is a generic scsi command line interface and very nice . What I am after is a generic bus enumerator API so apps like cd recorder or fxtv can use to locate the device in the absence of a specified device. Cheers -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [re]writable cdrom drive
Amancio Hasty wrote... Amancio Hasty wrote... I have to agree with Matt on this plus the set of defaults is system wide . What are you agreeing with him on? Why not quote what you're talking about? Is it possible to get a system bus enumeration from the system so a program such a cdrecord can attempt to make an intelligent decision as to which device is the cd recorder for instance we know that the system can print the device's name and its scsi address: If you want a bus number, there's a really easy way to get it: # camcontrol devlist EXABYTE EXB-10i 2.6 at scbus0 target 3 lun 0 (pass0,ch0) EXABYTE EXB-8500-85Qanx0 0415at scbus0 target 4 lun 0 (pass1,sa0) SEAGATE ST31230W 0510at scbus1 target 0 lun 0 (pass2,da0) SEAGATE ST32155N 0318at scbus1 target 1 lun 0 (pass3,da1) PLEXTOR CD-R PX-R412C 1.04 at scbus1 target 3 lun 0 (pass4,cd0) PLEXTOR CD-ROM PX-4XCS 1.04 at scbus1 target 6 lun 0 (pass5,cd1) SEAGATE ST34371N 0484at scbus2 target 0 lun 0 (pass6,da2) So, in this case, the bus,target,lun combination for my CD-R is 1,3,0. cdrecord itself also has a slightly more obtuse way of doing the same thing: # cdrecord -scanbus Cdrecord release 1.8a22 Copyright (C) 1995-1999 J_rg Schilling scsibus0: 0) * 1) * [ ... ] The camcontrol output is easier to figure out, though. Ken This is about ease of use . cdrecord in the absence of a device specification should query the bus and present the user with a choice of cd recorder devices ideally if there is one cd recorder it should go ahead an use it if such behavior is not desired then create an option "--confirm" to ask the user if its okay to use the "guessed" cd recorder. If you think cdrecord should do something different, talk to Joerg Schilling [EMAIL PROTECTED] about it. camcontrol is a generic scsi command line interface and very nice . What I am after is a generic bus enumerator API so apps like cd recorder or fxtv can use to locate the device in the absence of a specified device. There is a generic SCSI bus enumerator API, and one for PCI as well. There isn't a generic API to get trees of devices of any type in the system, though. With new-bus that might be possible, but having done two enumerator APIs already (I wrote the CAM and PCI enumerator code), I can predict that it might be very complicated to do properly. (Things get really hairy when you have to keep the device tree from changing while you're traversing it.) In any case, for the two applications you specified, cdrecord is only interested in SCSI devices, and there is already an API -- that cdrecord already supports -- to do bus/device enumeration. The cdrecord -scanbus code already uses that API. Similarly, there is already a PCI device listing interface, so fxtv should be able to easily pull out the devices it is interested in. All it has to do is search for all "meteor" or "bktr" devices to find what it wants. Ken Now how can I map a device name from this bus enumeration so that I can issue an "open" to the device: pciconf -l chip0@pci0:0:0: class=0x06 card=0x chip=0x12378086 rev=0x02 hdr=0x00 isab0@pci0:1:0: class=0x060100 card=0x chip=0x70008086 rev=0x01 hdr=0x00 ide_pci0@pci0:1:1: class=0x010180 card=0x chip=0x70108086 rev=0x00 hdr=0x00 chip1@pci0:1:2: class=0x0c0300 card=0x chip=0x70208086 rev=0x01 hdr=0x00 de0@pci0:9:0: class=0x02 card=0x11001385 chip=0x00091011 rev=0x22 hdr=0x00 bktr0@pci0:10:0:class=0x04 card=0x13eb0070 chip=0x036e109e rev=0x02 hdr=0x00 none0@pci0:10:1:class=0x048000 card=0x13eb0070 chip=0x0878109e rev=0x02 hdr=0x00 ahc0@pci0:11:0: class=0x01 card=0x chip=0x81789004 rev=0x00 hdr=0x00 ahc1@pci0:12:0: class=0x01 card=0x chip=0x71789004 rev=0x03 hdr=0x00 vga-pci0@pci0:13:0: class=0x03 card=0x0000 chip=0x0519102b rev=0x01 hdr=0x00 -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [re]writable cdrom drive
Amancio Hasty wrote...
There is a generic SCSI bus enumerator API, and one for PCI as well. There
isn't a generic API to get trees of devices of any type in the system,
though. With new-bus that might be possible, but having done two
enumerator APIs already (I wrote the CAM and PCI enumerator code), I can
predict that it might be very complicated to do properly. (Things get
really hairy when you have to keep the device tree from changing while
you're traversing it.)
In any case, for the two applications you specified, cdrecord is only
interested in SCSI devices, and there is already an API -- that cdrecord
already supports -- to do bus/device enumeration. The cdrecord -scanbus
code already uses that API.
Similarly, there is already a PCI device listing interface, so fxtv should
be able to easily pull out the devices it is interested in. All it has to
do is search for all "meteor" or "bktr" devices to find what it wants.
Ken
Now how can I map a device name from this bus enumeration so that I can issue
an "open" to the device:
pciconf -l
chip0@pci0:0:0: class=0x06 card=0x chip=0x12378086 rev=0x02
hdr=0x00
isab0@pci0:1:0: class=0x060100 card=0x chip=0x70008086 rev=0x01
hdr=0x00
ide_pci0@pci0:1:1: class=0x010180 card=0x chip=0x70108086
rev=0x00 hdr=0x00
chip1@pci0:1:2: class=0x0c0300 card=0x chip=0x70208086 rev=0x01
hdr=0x00
de0@pci0:9:0: class=0x02 card=0x11001385 chip=0x00091011 rev=0x22
hdr=0x00
bktr0@pci0:10:0:class=0x04 card=0x13eb0070 chip=0x036e109e
rev=0x02 hdr=0x00
none0@pci0:10:1:class=0x048000 card=0x13eb0070 chip=0x0878109e
rev=0x02 hdr=0x00
ahc0@pci0:11:0: class=0x01 card=0x chip=0x81789004 rev=0x00
hdr=0x00
ahc1@pci0:12:0: class=0x01 card=0x chip=0x71789004 rev=0x03
hdr=0x00
vga-pci0@pci0:13:0: class=0x03 card=0x chip=0x0519102b
rev=0x01 hdr=0x00
Only one of the above devices actually has a character device interface in
/dev. All you have to do is something like this:
sprintf(foo, "/dev/%s%d", p-pd_name, p-pd_unit);
The only way it would become complicated is if the device name in the
kernel were different than the device name in /dev.
Ken
Or if there is a system call or modification to open such that I can issue :
open("pci0:10:0", .)
On the kernel side, I hope that the pci code can translate a bus enumeration
to an actual major , minor device.
The only problem that I see with such an approach is security and I would
rather deal with that later.
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: [re]writable cdrom drive
Matthew Dillon writes: And to head off another question: When you are recording to a CD-RW you can do a 'quick erase' of the media using 'cdrecord blank=fast'. This does not actually erase the data, so if you have used say 100MB you will only have 550MB left. You can actually erase the media using 'cdrecord blank=all', which takes a while. In my experience, this is not true. I have used blank=fast on a CDRW that has over 500 MB written, and then written another 500 MB without a problem. I could be wrong;nevertheless, last nite I made a couple of CDs over 500MB with "blank=fast" and it worked. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cd writer recommendation?
You got to be joking . Is not that I do or don't want to write documentation is rather that I don't feel qualify to write such a document. Besides, the recent scrimmage between Jordan and Brian does not give me a warm fuzzy feeling to dive into writing the documentation. Have Brian write the doc. Cheers -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cd writer recommendation?
Lets see what the CAM people have to say about providing an interface to ATAPI CDs including CD recorders. On Tue, 17 Aug 1999, Kevin S. Brackett wrote: For a list of "reported to work" drives that work with cdrecord check out: http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdwriters-1.8.html Also, notice the "It should run on: All SCSI-3/mmc compliant drives, All ATAPI/mmc compliant drvies" The HP 7200 drive is listed, so maybe it will work with your drive. Hmm, actually it requires Linux's `scsi emulation layer' which makes atapi's look like scsi's (I know this is a simplification) - FreeBSD currently has no equivalent :) . Andrew. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb
A side note on gdb-4.18 8)
(gdb) run
Starting program: /tmp/./sieve
Program received signal SIGBUS, Bus error.
0x281eeac7 in GC_find_limit (p=0xbfbfcff8 "", up=1)
at ../../../../libgcj-2.95/boehm-gc/os_dep.c:681
681 ../../../../libgcj-2.95/boehm-gc/os_dep.c: No such file or directory.
Current language: auto; currently c
(gdb) cont
Continuing.
Running Sieve benchmark.
This will take about 10 seconds.
Breakpoint 1, Sieve.runSieve () at Sieve.java:16
16 int SIZE = 8190;
Current language: auto; currently java
(gdb) list
11 System.out.println(results1);
12 System.out.println(results2);
13}
14
15static void runSieve() {
16 int SIZE = 8190;
17 boolean flags[] = new boolean[SIZE+1];
18 int i, prime, k, iter, count;
19 int iterations = 0;
20 double seconds = 0.0;
(gdb) list
21 int score = 0;
22 long startTime, elapsedTime;
23
24 startTime = System.currentTimeMillis();
25 while (true) {
26 count=0;
27 for(i=0; i=SIZE; i++) flags[i]=true;
28 for (i=0; i=SIZE; i++) {
29 if(flags[i]) {
30prime=i+i+3;
It still needs a little work however gdb appears to work java programs
compiled with "gcj" -- GNU's java compiler -- java to native binary ..
gcj still needs work however it is starting to shape up.
Enjoy
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: [re]writable cdrom drive
Hi Guys Is me again 8) mkisofs -R /mount/dir | cdrecord -v fs=6m speed=2 -dev=0:1:0 Okay, whats the magic device name to access the yamaha cd recorder . I have tried several combinations of names with no success. dmesg says that I have: cd0 at ahc0 bus 0 target 1 lun 0 cd0: YAMAHA CRW6416S 1.0b Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not presen Tnks! -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cd writer recommendation?
Sorry about that . The emphasis is more on the hardware and second is the software -- I usually get around problems with the software. Is there any support for IDE CD writers or are they not worth bothering with on FreeBSD. Tnks! On Sun, 15 Aug 1999, Amancio Hasty wrote: Any one care to recommend a CD writer for FreeBSD-current since thats typically what I run over here. Are you asking for recommendation about hardware or software? It's not evident from your wording. Tnks -- Amancio Hasty [EMAIL PROTECTED] Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cd writer recommendation?
Most Cool! Is there a list of IDE cd writers which work FreeBSD? Tnks Again! On Mon, 16 Aug 1999, Amancio Hasty wrote: Sorry about that . The emphasis is more on the hardware and second is the software -- I usually get around problems with the software. Mkisofs is good for creating an ISO 9660 file systems. Wormcontrol and dd are a good combination for writing them. Is there any support for IDE CD writers or are they not worth bothering with on FreeBSD. Yes, there is support for them :) Tnks! On Sun, 15 Aug 1999, Amancio Hasty wrote: Any one care to recommend a CD writer for FreeBSD-current since thats typically what I run over here. Are you asking for recommendation about hardware or software? It's not evident from your wording. Tnks -- Amancio Hasty [EMAIL PROTECTED] Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linuxulator: emulation? [was: Q: Extending the sysctl MIB...]
I think that emulation usually denotes simulation so I would find another term or invent one to describe the linux emulation layer. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cd writer recommendation?
Cool, So can we have the manufacture and model of your cd-recorder ? 8) Browsing a little over at http://www.buy.com and noticed that they have quite a few Plextor cd recorders so I am wondering if anyone has any experience with Plextor cd recorders... Tnks! -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linuxulator: emulation? [was: Q: Extending the sysctl MIB...]
And whats Whistle market capitilization since becoming part of IBM ? 8) On Mon, 16 Aug 1999, Tom Bartol wrote: I absolutely agree with Jordan on this point. I'm having an increasingly hard time keeping our lab running FreeBSD over Linux due to pressure from higher-ups who aren't in the technical trenches with me and who don't understand the very good technical reasons I have for running FreeBSD here. One constant sticking point is the linux compatibility module. The higher-ups see the word "emulator" and all manner of warning messages go off in their uninformed heads. In a previous e-mail on this or a related thread I saw the term: "Linux image activator" or something close to this pass by. I think this term gave me a much closer feeling to what I imagine is really going on the the "linuxulator" than the term "emulator" and all its baggage. So we could name it the "Linux image activator" or "Lin-Axe" or some such... I'd just like to have it described as running a program in "linux mode" In Linux mode, FreeBSD appears exactly a s alinux muchine would to a Linux program and the program can run un-modified. (Now that Red Hat has a market capitialisation of 5Billion$ there will be a lot more linux stuff available) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linuxulator: emulation? [was: Q: Extending the sysctl MIB...]
Well, okay. They are sort of hiding the fact that they are using FreeBSD and you will have to ask them why is FreeBSD is not more prominently advertised. Not too long ago I read a review on various internet appliances and Whistle listed their OS as BSD/UNIX. On the other hand, Juniper does have a nice web article on why they are using FreeBSD 8) And I have to kill this thread lets continue on -chat Cheers -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linuxulator: emulation? [was: Q: Extending the sysctl MIB...]
Okay, I will bite. What would you call the linux emulator to convey the proper meaning to the suits types? -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cd writer recommendation?
I take it that the absence of the interface means your cd-recoder uses scsi. Tnks A Lot! So can we have the manufacture and model of your cd-recorder ? 8) Yes, it's a "Smart and Friendly" (gah!) "Rocket Recorder" - it does 8X CDR, 6X CDRW and 24X CD. I like it. :) - Jordan -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cd writer recommendation?
Oh Guys, I simply am trying to get information on which cd-recorder works well on FreeBSD. It will help to avoid confusion and postings if there was a cd-record handbook section explaining all the gory details. Peace -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sh still is not working for MAKEDEV
Well, he can run "ktrace -di ./MAKEDEV whatever" then kdump foo.dump Or compile sh with debug symbols and trace down the failure. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unkillable processes
while you are at it try to compile a kernel with symbols ... -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unkillable processes
On Sun, 25 Jul 1999, Amancio Hasty wrote: while you are at it try to compile a kernel with symbols ... I already have (this is my standard practice). What should I do with it here? Kris Well, if the process is not in a zombie state and you can't kill it . We may need to examine the process structure. Cheers -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Soft-updates feedback
Have you checked your syslog to see if you are getting disk errors? Also, I noticed that you have a VIA chipset and I know that at least with the Bt848 driver they have caused havoc. I would stick to Intel PCI chipsets. Not sure if your motherboard supports or not do you have the latest microcode for your VIA chipset? Cheers -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Soft-updates feedback
Glad that is working out for you. I am not into PCI low level bugs they are very difficult to indentify and in certain cases impossible to fix. To give you a little hint: 1.6825 May 1999 Roger Hardiman [EMAIL PROTECTED] Due to differences in PCI bus implementations from various motherboard chipset manufactuers, the Bt878/Bt879 has 3 PCI bus compatibility modes. These are NORMAL PCI 2.1 for proper PCI 2.1 compatible chipsets. INTEL 430 FXfor the Intel 430 FX chipset. SIS VIA CHIPSET for certain SiS and VIA chipsets. Older Intel and non-Intel chipsets may also benefit from either 430_FX or SIS/VIA mode. Usually, the kind of problems that I have heard of is systems hanging hard for instance with the Bt848 driver. The bottom line is that if it is working for you great. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: LDAPed FreeBSD
Again, I think it is appropiate to use LDAP for configuring network services such as DHCPD , DNS , PPP, etc and to a limited extend sendmail -- see sendmail's modification to support user's delivery address : http://www.stanford.edu/~bbense/Inst.html and actually We can ask the Standford team about some of the problems mentioned on this list to see what they think about it ;specially, if their LDAP service is deployed ... True LDAP (v2 or v3) does not provide record locking . Now the question is does Novell's NDS 8 -- a native LDAP v3 -- , Oracle's Directory Server or Microsoft Active Directory does if they do then how ? Mantaining state information such as DNS is not a good idea as Kurt has stated . Again my emphasis is on configuring network services or other system services if appropiate and to provide a HTML interface which is sufficiently rich to be user friendly. My little test bed project is coming along fine . My servlet which implements my dummy html interfface, http://www.star-gate.com/dhcpd.html, is fully operational and it was not hard to wirite whats left is to provide error checking and cross data validation . The mods to dhcpd to support ldap are already in place. Searching the LDAP database for existing DHCPD entries is also fairly straight forward and I do have a servlet to locate dhcpd servers which accepts regular expressions as suppported by LDAP --- search : www* will locate all the dhcdp servers starting with www 8) Regards At 02:29 PM 7/4/99 -0700, Amancio Hasty wrote: Record locking and batch requests is a bit more difficult to solve perhaps someone in the list can shed light into this problem for instance does LDAPv3 provide such mechanism? LDAP (v2 or v3) does not provide record locking, client/server transactions, nor any specific batching requests. The "L" in LDAP means lightweight. I think LDAP-based directory service could be used to manage a wide variety of system information including configuration information for various other network services. However, using LDAP directory services to manage network-services state information is likely not appropriate application of LDAP. For example, while it may make sense to use an LDAP directory service to manage the configuration and master zone information for a Domain Name Service, it would not be wise to use an LDAP directory service to maintain state information (such records created due to DHCP operations) of Domain Name Service. If there any bugs in the ldap server I will probably fix them or better yet the people working on openldap will fix them. OpenLDAP, like FreeBSD, is user maintained and developed. All users are encouraged to contribute to the project. We can surely use your help! Kurt -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: loads of SetAttrs in cvsup of cvs repo
Curious why are you cvsupping every couple of minutes ? -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: loads of SetAttrs in cvsup of cvs repo
Arghh... Yeap, upon reading the original message again it reads as you have stated . I need more sleep ... 8) Tnks On Sun, 4 Jul 1999, Amancio Hasty wrote: Curious why are you cvsupping every couple of minutes ? I think what was meant was that the CVSup process takes a few minutes usually, but has taken over an hour now. - alex I thought felt your touch In my car, on my clutch But I guess it's just someone who felt a lot like I remember you. - Translator -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
