--- current-digest <[EMAIL PROTECTED]> wrote: > > current-digest Tuesday, October 26 1999 > Volume 04 : Number 679 > > > > In this issue: > Re: lsof broken > Nevermind! (Re: Info needed re: new userconfig > scripting and PnP) > [none] > Re: freefall hangs w/ nfs > Re: freefall hangs w/ nfs > ACPI project started in Japan > Re: pcm/ES1370 PCI soundcard problem > Re: [Call for review]: newsyslog - new option > Re: trek73 > Re: make world failing on current > Re: trek73 > Re: trek73 > Re: Info needed re: new userconfig scripting and PnP > Re: trek73 > Re: trek73 > Re: trek73 > Re: Anyone adding "support" for Athlons. > Re: linux emulation broken.. (solution) > Re: linux emulation broken.. (solution) > Newmidi updated (CS461x, GUS, pcm+midi, etc) > Re: freefall hangs w/ nfs > Re: AMRD (MegaRAID) BIOS rev another other questions > > ---------------------------------------------------------------------- > > Date: Mon, 25 Oct 1999 11:43:12 +0200 > From: Sheldon Hearn <[EMAIL PROTECTED]> > Subject: 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-aa 1997/02/04 08:30:22 1.2 > +++ patch-aa 1999/10/25 09:39:34 > @@ -1,6 +1,15 @@ > --- dialects/freebsd/machine.h.orig Fri 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 > ++/* #define HASNCACHE 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 > > ------------------------------ > > Date: Mon, 25 Oct 1999 06:37:44 -0500 (CDT) > From: Conrad Sabatier <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Mon, 25 Oct 1999 08:48:34 -0400 (EDT) > From: Dave Seaman <[EMAIL PROTECTED]> > Subject: [none] > > help subscribe > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Mon, 25 Oct 1999 07:36:26 -0700 (PDT) > From: David Wolfskill <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Mon, 25 Oct 1999 10:26:04 -0700 (PDT) > From: Matthew Dillon <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Tue, 26 Oct 1999 02:49:32 +0900 > From: Mitsuru IWASAKI <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Mon, 25 Oct 1999 21:06:53 +0200 > From: Ollivier Robert <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Mon, 25 Oct 1999 21:25:09 +0200 > From: Gary Jennejohn <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Mon, 25 Oct 1999 12:33:55 -0700 (PDT) > From: Kris Kennaway <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Mon, 25 Oct 1999 21:37:06 +0200 > From: Ollivier Robert <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Mon, 25 Oct 1999 15:21:00 -0500 (CDT) > From: Jim Bryant <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Mon, 25 Oct 1999 13:29:44 -0700 (PDT) > From: Kris Kennaway <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Mon, 25 Oct 1999 17:37:06 +0100 > From: Nik Clayton <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Mon, 25 Oct 1999 16:12:47 -0500 (CDT) > From: Jim Bryant <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Mon, 25 Oct 1999 17:30:40 -0400 (EDT) > From: Ben Rosengart <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Mon, 25 Oct 1999 18:05:31 -0500 (CDT) > From: Jim Bryant <[EMAIL PROTECTED]> > Subject: 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<tm>, 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 > > ------------------------------ > > Date: Mon, 25 Oct 1999 17:01:05 -0700 > From: "David O'Brien" <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Mon, 25 Oct 1999 20:22:16 -0500 > From: Chris Csanady <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Mon, 25 Oct 1999 21:28:01 -0400 (EDT) > From: Chuck Robey <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Tue, 26 Oct 1999 13:52:58 +0900 > From: Seigo Tanimura > <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Tue, 26 Oct 1999 12:10:57 +0400 > From: Dmitrij Tejblum <[EMAIL PROTECTED]> > Subject: Re: freefall hangs w/ nfs > > Matthew Dillon wrote: > > Actually, what I meant was that AMD itself is > equivalent to a loopback > > mount, whether or not you make loopback mounts > through it. > > No. The loopback deadlock happen when the nfs server > handle a write > operation. But there cannot be any writes in the amd > filesystem. The > filesystem only contains symlinks to outside. > > Dima > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Tue, 26 Oct 1999 11:26:47 +0100 > From: Geoff Buckingham <[EMAIL PROTECTED]> > Subject: Re: AMRD (MegaRAID) BIOS rev another other > questions > > On Sun, Oct 24, 1999 at 09:58:11AM -0600, Greg Lehey > wrote: > > > > Indeed. It's quite easy to put all cylinder > groups on a single > > spindle; I've seen reports of up to 80% > degradation under these > > circumstances. > > > > > Where sequential read/write performance is not > critical you can stripe at > > > cluster size to avoid this. Other wise using an > odd number of spindles for > > > a stripe and an even number for a RAID3 or RAID5 > or stripeing at an interval > > > which is not a power of two should work > (12,24,48,76 etc) > > > > The best I've heard of is 768 kB - 1 sector. This > works on Vinum, but > > it seems that most RAID controllers use a somewhat > simplistic striping > > algorithm. You might like to try 31 kB or such. > This won't make any > > difference with rawio, though. > > > > I would agree from experiance that 768 KB seems a > good selection for vinum > and probably ccd too > > - -- > GeoffB > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > End of current-digest V4 #679 > ***************************** > > ===== __________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
