Re: it's time...
On Tue, 10 Aug 1999, Alex Zepeda wrote: :* an rc.audio or rc.multimedia (this could perhaps contain some bt484 :related things). : :But if it goes into "the" rc.conf, that would mean that whenever it runs :at shutdown, it edits rc.conf; this isn't IMO a real great idea. :Anything automated (even sysinstall) editing rc.conf in any way shape or :form makes me leery because it's so much more error prone. Why not create such a file, and update it whenever a change is made? The settings are always in whatever state you last set them to, no matter when it was, and you don't have to race shutdown. Jamie Bowden -- If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: rpc.lockd and xdr.
On Mon, 6 Mar 2000, David E. Cross wrote: :Version 2 of the lock manager is ready to be released. Amitha :says that it passes all of the tests in the suite posted by Drew (thanks :Drew). A noteable exception to this is on SGI where some lock requests :are never even received from the remote host. Also DOS sharing is not :yet complete. Any idea why this is? I only ask because: 12:12pm banshee /home/jamie %uname -aR IRIX64 banshee 6.5 6.5.5m 07151433 IP25 I have some PC's that I'm interested in putting FreeBSD on (other than my laptop) that would be on the network fulltime, and working NFS locking is really the only stumbling bock for me now. Jamie Bowden -- "Of course, that's sort of like asking how other than Marketing, Microsoft is different from any other software company..." Kenneth G. Cavness To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /usr/ports/xll/XFree86-4
On Wed, 3 Dec 2003, Dan Nelson wrote:
> In the last episode (Dec 03), Mike Hunter said:
> > On Dec 02, "Jamie Bowden" wrote:
> > > I have a new machine that I've just installed 5.1-R on, and cvsup'd
> > > to -C. I'm attempting to build X, and am getting a core dump from
> > > rman during the process.
> >
> > I had this happen too. I did something really hack-ish to get around
> > it (like delete that documentation or some other unspeakable hack.)
>
> The coredump is due to bugs in the rman command (which is installed by
> the imake port, believe it or not). I submitted a bugreport on it in
> July, and hopefully it will be in Xfree86 4.4.0. Installing the
> textproc/rman port may mask the bug until then, or you can drop this
> file into ports/devel/imake-4/files and rebuild imake.
Installing /usr/ports/emulators/linux_compat seems to fix this. I have no
idea why, but I went ahead and installed it so I could install the Nvidia
X driver. After I did that (built and installed linux_compat and built
and installed the Nvidia driver), I went ahead and re-entered
x11/XFree86-4/ and did a make install again (mostly just looking for the
error so I could comment the lines out of the makefile), and it built and
installed (after I rebuilt and reinstalled imake-4, just on principle).
There's an odd dependency hiding in there somewhere.
Now I just have to figure out why X only believes this LCD is capable of
640x480 or 320x240 instead of the 1920x1600 it's actually capable of, so
back to -mobile I go.
Jamie Bowden
--
"It was half way to Rivendell when the drugs began to take hold"
Hunter S Tolkien "Fear and Loathing in Barad Dur"
Iain Bowen <[EMAIL PROTECTED]>
--- ../extras/rman/rman.c.orig Tue Jul 15 23:53:53 2003
+++ ../extras/rman/rman.c Tue Jul 15 23:44:21 2003
@@ -4104,6 +4104,9 @@
}
}
break;
+case 0:
+ /* ignore */
+ break;
default: /* unknown escaped character */
sputchar(*p++);
}
@@ -4133,7 +4133,7 @@ source_out0(const char *pin, char end)
/* postpone check until after following character so catch closing tags */
if ((sI>=4+1 && plain[sI-1-1]==')') ||
/* (plain[sI-1]==' ' && (q=strchr(plain,' '))!=NULL && q<&plain[sI-1])) */
-(plain[sI-1]==' ' && !isalnum(plain[sI-1-1]))) {
+(sI>=2 && plain[sI-1]==' ' && !isalnum(plain[sI-1-1]))) {
/* regardless, flush buffer */
source_flush();
}
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any users of matcd(4), mcd(4), or scd(4)?
On Thu, 3 Oct 2002, John Baldwin wrote: :Are there any users who use the matcd(4), mcd(4) or scd(4) drivers? :These drivers are for rather old non-standard CD-ROM controllers :most of which only support 1x speeds. :) There are several changes :being made to the kernel API's used by device drivers in -current. :Unless we can find some people who actually use these devices and :can test patches for these drivers we will have to drop support for :them. So, is anyone out there still using this old hardware? Note :that if support for these ancient devices was dropped, it wouldn't :be dropped until 5.0. 4.x. would continue to support these devices :forever. I have an old ISA SB16 with the matcd interface on it and the 2x Creative (Matsushita/Panasonic) CD-ROM drive that goes with it. I'd be more than happy to ship these off to the project if the project wants them. Last time I bothered to plug them into a machine and check them, they were still functional. Jamie Bowden -- "It was half way to Rivendell when the drugs began to take hold" Hunter S Tolkien "Fear and Loathing in Barad Dur" Iain Bowen <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
