Newmidi updated (CS461x, GUS, pcm+midi, etc)
After a long absense, newmidi now supports CS461x/428x PCI Audio and GUS midi, with some bug fix. Both pcm and midi on an ISA PnP/ PCI card now work(for SB/GUS/CS461x). Microtimeout and APIC timer patches are separated from newmidi. Please follow the document at: http://www.freebsd.org/~tanimura/newmidi/ to install newmidi. Thanks! Seigo Tanimura <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: linux emulation broken.. (solution)
On Mon, 25 Oct 1999, Chris Csanady wrote: > > I *know* someone else said it wasn't so, but just 3 weeks ago I had this > > very problem, with word perfect, and it works just fine now. Are you sure > > you have a really up to date linux_base port installed? It was recently > > changed, a *lot* of new libs added, and I'd really like an answer on this, > > whether I'm right or wrong. > > Well, I found a solution to my problems with running linux-netscape and word > perfect. It looks like it was not the linux emulation code that was at fault. > > I recently installed a real redhat 6.1, and mounted it on /compat/linux. Now > all is well--so I can only assume it is some weird interaction between the > linux_base port and my system. Maybe it is related to using XFree86 3.9.15, > but I don't have the time to test that theory right now. > > Certainly not a great solution, but if things are broke for you this at least > works. No, like I said, when I *really* updated my Linux libs (and the linux_base port had very newly updated libs when I posted this) my problems evaporated, which is why I urged others to do it. I don't know why it didn't work for you, but at least it's done for you now. > > Chris Csanady > Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: linux emulation broken.. (solution)
> I *know* someone else said it wasn't so, but just 3 weeks ago I had this > very problem, with word perfect, and it works just fine now. Are you sure > you have a really up to date linux_base port installed? It was recently > changed, a *lot* of new libs added, and I'd really like an answer on this, > whether I'm right or wrong. Well, I found a solution to my problems with running linux-netscape and word perfect. It looks like it was not the linux emulation code that was at fault. I recently installed a real redhat 6.1, and mounted it on /compat/linux. Now all is well--so I can only assume it is some weird interaction between the linux_base port and my system. Maybe it is related to using XFree86 3.9.15, but I don't have the time to test that theory right now. Certainly not a great solution, but if things are broke for you this at least works. Chris Csanady To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone adding "support" for Athlons.
> I've not got an up to date version of gcc available at the moment (will get > -current over the weekend however and see how things change) see /usr/ports/lang/egcs/ > (Not sure why we have two version of gas in the source tree though ?) The first is our ELF linker, the second is our a.out linker. > -rw-r--r-- 1 root wheel 43061 Sep 6 1998 > /usr/src/contrib/binutils/include/opcode/i386.h > > -rw-r--r-- 1 root wheel 34662 Mar 29 1998 > /usr/src/gnu/usr.bin/as/opcode/i386.h > But they don't yet seem to be in even the egcs cvs tree. (well they > weren't on Wednesday) the "egcs" tree (src/contrib/egcs/) is EGCS-1.1.2 and is not being updated. A newer compiler is in the works (and will live elsewhere). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trek73
In reply: > On Mon, 25 Oct 1999, David Schwartz wrote: > > > > > "unauthorized" things for keeping Trek alive in the first place... If > > > > it came out that Paramount ever tried litigation over such things, > > > > they would lose a LOT of fans, and the money in their pockets! What > > > > would come next? Sueing people at conventions for getting the > > > > uniforms wrong? > > > > > > Or sueing fan websites, perhaps? > > > > Isn't this more or less precisely what happened once X-Files > > became popular enough to not need them anymore? > > Yup - but my point was that at around the time of the debut of > www.startrek.com, the Paramount lawyers went on a spree, marking their > territory by threatening high-profile fan sites. Whether or not it's > something which would stand up in court, it's hassle the project could do > without, and leaving aside the issue of whether the existing trek(6) > should remain I wouldn't want to tempt fate by adding a second. > > Amusingly, Paramount are now claiming trademark on the letter 'Q'. > > Kris They can threaten all they want. The risk of actual action against trek73 is infinitesimally small. Even an injuntion would be extremely hard to get because they have to prove that it would hurt their reputation or income to not get an injunction. This game does neither, and such an injunction would be counter-productive. The questions are: Where on this planet will they find a jury to take their side? And, how bad will such hostile actions on the part of Paramount hurt their bottom line, knowing that their audience is extremely computer literate on the average, and that a large percentage of them have at least heard of the game or similar public-domain games. The answers, of course, are: Nowhere, and badly. You don't just up and insult the most loyal following of any series in history, and expect the fans not to take it personally. Are they going to sue NBC for putting the episodes of SNL with Star Trek parodies into syndication? How about the NUMEROUS other TV shows that have parodied it? Or even suing comics who parody the show? Paramount has produced "official" fan pieces that pride themselves on such recognition. No matter what Lush Rimbaugh says on the topic, frivilous lawsuits RARELY win in court. A lawsuit over this would indeed be frivilous. I'll now repeat the OLD joke: "Capt. Kirk is chasing Klingons around Uranus!"... Think they'll sue because I said that? That joke is so old that it has petrified. If they are actively threatening fan web-sites, it's time for a boycott of Paramount. Pissing off Trek fans would be a monumental mistake, there are an awful lot of us. I've pretty much made my position clear, but it's not up to me, it's up to -core. I say put trek73 in! With as many Trek fans that use open-source operating systems, a boycott counter-threat might just work. That includes boycotting sponsors. Scott me up, Beamie! This planet sucks! jim -- All opinions expressed are mine, if you| "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" -- [EMAIL PROTECTED] - KC5VDJ HF to 23cm grid: EM28pw - http://www.tfs.net/~jbryant -- IC-706MkII - IC-T81A - HTX-202 - HTX-212 - HTX-404 - KPC3+ - PK-232MBX/DSP To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trek73
You're talking as if litigious corporations follow logic and common sense. This is more the exception than the rule IMO. Don't construe this as arguing against the inclusion of trek73 ... I think you're probably right that the risk is minimal, but for different reasons. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trek73
In reply: > > On Mon, 25 Oct 1999, Jim Bryant wrote: > > > > > "unauthorized" things for keeping Trek alive in the first place... If > > > it came out that Paramount ever tried litigation over such things, > > > they would lose a LOT of fans, and the money in their pockets! What > > > would come next? Sueing people at conventions for getting the > > > uniforms wrong? > > > > Or sueing fan websites, perhaps? > > Isn't this more or less precisely what happened once X-Files became popular > enough to not need them anymore? > > DS In case you haven't noticed... The current Trek series' have an ever-dwindling audience. The ONLY thing keeping Voyager alive is widely accepted to be the Borg chick with the extremely fine hooters and the pouty voice. Their litigation money would be better spent going after those unauthorized items that are commercial products, and there is an endless supply of those. If litigation was ever threatened over this CLASSIC public-domain 27 year old game, we can always dig up interviews with the stars and producers to back us up. All true Trekkies have heard the interviews. Trek has always been an underground phenomenon. This game has existed in various forms since 1973, and has never been a commercial product. Paramount would be hard-pressed to prove that they have lost one dime as a result of this game. Burdon of proof is on the litigant. This game in fact when put side by side with a modern trek game in front of a jury would only prove to a jury how frivilous and petty such a suit would be in the first place. The Trek sub-culture is unique. A universe without money, where prestige is based on accomplishment, and not what family you were born into or how big your bank accounts are. Ten or fifteen years earlier, and the right wing would have blackballed Roddenberry as a commie. "Humans are capable of so much more than we yet understand. We're really something! Star Trek fans really believe that, and so do I." -- Gene Roddenberry jim -- All opinions expressed are mine, if you| "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" -- [EMAIL PROTECTED] - KC5VDJ HF to 23cm grid: EM28pw - http://www.tfs.net/~jbryant -- IC-706MkII - IC-T81A - HTX-202 - HTX-212 - HTX-404 - KPC3+ - PK-232MBX/DSP To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Info needed re: new userconfig scripting and PnP
On Sun, Oct 24, 1999 at 02:10:03PM -0500, Conrad Sabatier wrote: > Someone just mailed me this heads up about my AWE soundcard setup > tutorial at http://members.home.net/conrads/awepnp-freebsd.html. > As this is the first I've heard about this, I'd greatly appreciate it Conrad (and anyone else with tutorials like this). This could fit neatly under doc/en_US.ISO_8859-1/articles/, if you'd care to. That would get it in the CVS tree (for ease of maintenance), allow the translation teams to tackle it, and get it mirrored on all the FreeBSD mirrors around the world. Interested? N To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trek73
On Mon, 25 Oct 1999, Jim Bryant wrote: > "unauthorized" things for keeping Trek alive in the first place... If > it came out that Paramount ever tried litigation over such things, > they would lose a LOT of fans, and the money in their pockets! What > would come next? Sueing people at conventions for getting the > uniforms wrong? Or sueing fan websites, perhaps? > The boggle(6) incident has probably cost it's manufacturer lost sales, > because they played the incident like jerks. I cheered when they were > named in the Toys-R-Us class-action lawsuit, because they were such > jerks here. I doubt it. Most people who followed the debate on FreeBSD-hackers probably weren't likely to buy a copy of boggle anyway. Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trek73
In reply: > On Sat, 23 Oct 1999, Matthew Dillon wrote: > > > I found a copy of the C version of trek73 in my Amiga archives. This > > is the trek73 originally written in HP-2000 Basic that was rewritten > > by Dave Pare and Chris Williams in C and seriously enhanced by a bunch > > of people including me in my early college years circa 1985. > > > > I don't think any of the authors would mind if it went into /usr/games, > > but tracking them down is close to impossible since ucbvax no longer > > exists. If nobody knows different, I would like to clean it up (fairly > > easy since it's already in C) and commit it in. > > Is it worth worrying about trademark issues [1]? We still have trek in the > base system, but adding a second version might wake the lawyers. > > Kris > > [1] See boggle(6) Gimme a break... If Paramount wanted to go after "unauthorized" trek paraphenalia, they have much larger fish to fry than a CLASSIC public-domain trek game distributed with a FREE operating system that tens or even hundreds of thousands of people have played over a period of nearly 30 years. I believe I have even heard Shatner himself in interviews credit such "unauthorized" things for keeping Trek alive in the first place... If it came out that Paramount ever tried litigation over such things, they would lose a LOT of fans, and the money in their pockets! What would come next? Sueing people at conventions for getting the uniforms wrong? The boggle(6) incident has probably cost it's manufacturer lost sales, because they played the incident like jerks. I cheered when they were named in the Toys-R-Us class-action lawsuit, because they were such jerks here. Bottom line: such games do not hurt the sales of any commercial product. Litigation against such games only hurt the reputation of the one bringing or threatening the litigation in the first place, and tends to make them look like assholes in the eyes of the public. [1] See boggle(6), which by the way compiles fine from the net(n) distributions, plus all of the 4.4 distributions. To hell with Hasbro. The BSD game would have survived patent infringement suit, it was not an EXACT duplicate, it actually had improvements over the dice game. Improve a patented item, and you can do anything you want. I cannot say that Paramount wouldn't do it, but I can say that if it did, it would detrimentally effect the entire Trek sub-culture; and they are perfectly aware of this fact, such things have been mentioned in interviews with the stars and producers in a POSITIVE light time and time again. I can probably arrange a statement from at least three of the stars of the original series to this effect. I may just do that, maybe I can get a statement from all of the surviving members of the original cast. The have made it clear in the past that they credit their ongoing fame to such underground paraphenalia. jim -- All opinions expressed are mine, if you| "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" -- [EMAIL PROTECTED] - KC5VDJ HF to 23cm grid: EM28pw - http://www.tfs.net/~jbryant -- IC-706MkII - IC-T81A - HTX-202 - HTX-212 - HTX-404 - KPC3+ - PK-232MBX/DSP To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make world failing on current
According to Dana Huggard: > /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c > *** Signal 12 You need to build and run a new kernel before. There were some changes that require that. You need to read all -current mails... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trek73
On Sat, 23 Oct 1999, Matthew Dillon wrote: > I found a copy of the C version of trek73 in my Amiga archives. This > is the trek73 originally written in HP-2000 Basic that was rewritten > by Dave Pare and Chris Williams in C and seriously enhanced by a bunch > of people including me in my early college years circa 1985. > > I don't think any of the authors would mind if it went into /usr/games, > but tracking them down is close to impossible since ucbvax no longer > exists. If nobody knows different, I would like to clean it up (fairly > easy since it's already in C) and commit it in. Is it worth worrying about trademark issues [1]? We still have trek in the base system, but adding a second version might wake the lawyers. Kris [1] See boggle(6) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Call for review]: newsyslog - new option
Hellmuth Michaelis writes: >I've added a new option (-o directory) to newsyslog to move the old logfiles >into another directory than the original ones. > works OK for me, although the English (Germish ?) in the man page could use some polishing. I only tested it using an absolute path. --- Gary Jennejohn Home - [EMAIL PROTECTED] Work - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm/ES1370 PCI soundcard problem
According to Marc van Woerkom: > device pcm0 at pci0 > > in the kernel configuration file. Try device pcm0 -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ACPI project started in Japan
Just FYI, We launched ACPI project in Japan today, but the activities haven't detailed yet in this project. We'd like to contribute something from this project to FreeBSD main stream developing some sort of prototype but don't want to make duplicated efforts anyway. So please let us know if you are doing something on ACPI. Suggestions, questions and requests are very appreciated. Please see http://www.jp.FreeBSD.org/acpi/ For more info. Mr. watanabe, on behalf of the project :), made some survey at FreeBSDCon. Doug Rabson, Mike smith and Warner Losh are interested in this area, and already some code was written. We'd like to keep consulting and cooperating with them. For the time being, we will make clean our experimental ACPI device deriver up, and may implement S5 Soft Off State transition by ACPI. And, we are going to make this kind of project report in English from time to time. # sorry for our poor English ;) Thanks! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: freefall hangs w/ nfs
:
:>Date: Sun, 24 Oct 1999 00:42:12 -0700 (PDT)
:>From: Matthew Dillon <[EMAIL PROTECTED]>
:
:>It looks on the face of it that AMD is hanging. Perhaps this is
:>preventing the system from clearing out buffers and causing lockups
:>on other mounts. AMD could also be causing a deadlock to occur in the
:>buffer cache (for the same reason loopback mounts can cause deadlocks).
:
:>The next time this happens, if the person rebooting freefall can get
:>a kernel dump (and have a corresponding debug kernel) I may be able to
:>track it down for sure. Fixing it is another problem, though. Loopback
:>deadlocks are a big problem under 3.x.
:
:In an environment where there is use of amd and NFS, there is no need
:for loopback NFS mounts.
Actually, what I meant was that AMD itself is equivalent to a loopback
mount, whether or not you make loopback mounts through it.
In looking at freefall a bit more, I don't quite understand why amd is
being used at all. I would simply create a /net/freefall/{c,d,g,x}
and mount /c, /d, /g, and /x there locally. Then on hub and bento the
same paths would simply be NFS mounts.
This would allow everyone's home directories to be hard coded on all
machines to /net/freefall/blahblahblah.
This is essentially what I did when we had shell1 and shell2 during the
early days of BEST.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: freefall hangs w/ nfs
>Date: Sun, 24 Oct 1999 00:42:12 -0700 (PDT)
>From: Matthew Dillon <[EMAIL PROTECTED]>
>It looks on the face of it that AMD is hanging. Perhaps this is
>preventing the system from clearing out buffers and causing lockups
>on other mounts. AMD could also be causing a deadlock to occur in the
>buffer cache (for the same reason loopback mounts can cause deadlocks).
>The next time this happens, if the person rebooting freefall can get
>a kernel dump (and have a corresponding debug kernel) I may be able to
>track it down for sure. Fixing it is another problem, though. Loopback
>deadlocks are a big problem under 3.x.
In an environment where there is use of amd and NFS, there is no need
for loopback NFS mounts.
The reason is that in addition to its "classical" role of simulating an
NFS mount, amd is also quite capable of simulating a symlink.
I ended up doing some of that as part of my first exposure to FreeBSD
(when I started here at Whistle) because otherwise, my desktop would
crash just about any time I tried to use "make".
A (slightly re-formatted for legibility) example of an amd map that
accomplishes the distinction is:
/defaults sublink:=${key}
* host!=shrimp;os==freebsd4;rhost:=shrimp;type:=nfs;\
rfs:=/shrimp/tribe;fs:=${autodir}/shrimp/tribe;\
opts:=vers=2,proto=udp,rw,intr,nosuid,grpid \
host!=shrimp;os==freebsd3;rhost:=shrimp;type:=nfs;\
rfs:=/shrimp/tribe;fs:=${autodir}/shrimp/tribe;\
opts:=vers=2,proto=udp,rw,intr,nosuid,grpid \
host!=shrimp;os!=freebsd3;rhost:=shrimp;type:=nfs;\
rfs:=/shrimp/tribe;fs:=${autodir}/shrimp/tribe;\
opts:=nfsv2,noconn,rw,intr,nosuid,grpid \
host==shrimp;type:=link;fs:=/shrimp/tribe
The key notion is embodied in that last line -- if the client is
"shrimp" (which happens to be the name of the server), don't use NFS;
rather, fabricate a symlink.
Yes, I realize that this doesn't fix the problem that plagues loopback
NFS mounts; it avoids the issue instead.
But sometimes it's appropriate to make things work, even if it's not the
ideal solution. Making that judgement call is not something I'm
prepared to do in this case; I'm presenting an alternative that has
worked for me, in cases where I have made that call.
Cheers,
david
--
David Wolfskill [EMAIL PROTECTED] UNIX System Administrator
voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
No Subject
help subscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Nevermind! (Re: Info needed re: new userconfig scripting and PnP)
OK, I've gotten a few private replies (thanks!), and have also read through several threads in the -current archives. I think I've got the picture now. Can't say I'm all that happy about what I've read (I mean, having to add to my web pages something to the effect of "you can disregard all of this information if you're running -current"), but who am I to stand in the way of progress, eh? :-) BTW, speaking of device IDs, if anyone needs the info for the AWE 64 "value" card, I'll be happy to provide whatever I can. -- Conrad Sabatier http://members.home.net/conrads/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: lsof broken
On Sun, 24 Oct 1999 23:32:42 -0400, Chuck Robey wrote: > It's broken trying to work with the name cache, and dies because it can't > find the name NCACHE. Where is this guy? I use the following patch to patches/patch-aa for CURRENT. I've no idea what this does to STABLE. Ciao, Sheldon. Index: patches/patch-aa === RCS file: /home/ncvs/ports/sysutils/lsof/patches/patch-aa,v retrieving revision 1.2 diff -u -d -r1.2 patch-aa --- patch-aa1997/02/04 08:30:22 1.2 +++ patch-aa1999/10/25 09:39:34 @@ -1,6 +1,15 @@ --- dialects/freebsd/machine.h.origFri Jan 17 23:15:41 1997 +++ dialects/freebsd/machine.h Tue Feb 4 17:23:58 1997 -@@ -291,7 +291,7 @@ +@@ -217,7 +217,7 @@ + * cache whose cache and vnodes are linked by a capability ID. + */ + +-#define HASNCACHE 1 ++/* #defineHASNCACHE 1 */ + #define HASNCAPID 1 + + +@@ -355,7 +355,7 @@ * (the one that its user logged on with) of the lsof process. */ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Texas Chainsaw Monday
On Fri, 22 Oct 1999, Bill Paul wrote:
> > > install -c -s -o root -g wheel -m 555 mount_nwfs /vol2/release/sbin
> > > install: mount_nwfs: No such file or directory
> >
> > Ok, it seems that I found why mount_nwfs failed to build: I'm use
> > 'install' instead of ${INSTALL} in the libncp.
>
> Unfortunately, this has not fixed the problem: the build report for
> today (Oct 22) shows the same error.
Well, today (Oct 25) I've done my own 'make release' and it wents
fine (fix for netgraph.h sent to Julian). I think that the error message
that you saw, was caused by first 'installworld' - source tree was updated
but not rebuiled and 'make world' even didn't happens.
--
Boris Popov
http://www.butya.kz/~bp/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
