Re: Problem with PAM-AUTH for XFree86?
I am using yesterday's snapshot (12-27). /etc/pam.conf is dated 12/21. Tom Veldhouse [EMAIL PROTECTED] Mark Murray wrote: I just got my box up and running Current 12-27. ATA works great for = both drives now. However, I compiled XFree86 from the port and I chose = the options for RPC, Wraphelp.c, PAM and threads. When I start x (using = startkde), I get many many password prompts. I can only assume that the = PAM module used for athentication by XFree86 is broken. Is the owner = aware of this? I recompiled without PAM support and everything works as expected. Is your /etc/* up to date? Specifically /etc/pam.conf? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with PAM-AUTH for XFree86?
Nope! Not too tricky. Should this be added to the file permanantly, or perhaps as part of the port? Tom Veldhouse [EMAIL PROTECTED] Clive Lin wrote: On Mon, Dec 27, 1999 at 11:01:50PM -0600, Thomas T. Veldhouse wrote: Hello, I just got my box up and running Current 12-27. ATA works great for both drives now. However, I compiled XFree86 from the port and I chose the options for RPC, Wraphelp.c, PAM and threads. When I start x (using startkde), I get many many password prompts. I can only assume that the PAM module used for athentication by XFree86 is broken. Is the owner aware of this? I recompiled without PAM support and everything works as expected. Hi! I dunno if this is tooo tricky, but I added a single line to solved the same question as yours. the xserver line... X clive@cartier ~ tail -5 /etc/pam.conf # tricky tricky forgive me xserver authsufficient pam_permit.so no_use # If we don't match anything else, default to using getpwnam(). other authrequiredpam_unix.so try_first_pass other account requiredpam_unix.so try_first_pass X clive@cartier ~ -- CirX Clive Lin [EMAIL PROTECTED] FreeBSD - The Power to Serve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
where did /etc/make.conf go?
I have noticed that /etc/make.conf is missing from the current source tree and I can not find any mention of its removal anywhere. Where did it go? Tom Veldhouse [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: where did /etc/make.conf go?
Hi, I have noticed that /etc/make.conf is missing from the current source tree and I can not find any mention of its removal anywhere. Where did it go? See /etc/defaults ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: General ata grousing
On Mon, 27 Dec 1999, Warner Losh wrote: In message [EMAIL PROTECTED] Peter Wemm writes: : Just as a BTW, dfr and sos are exchanging patches right now (and have been : for quite a few days) that happen to fix the inthand_add() stuff. This may also help the pccard code cases which I have floating around. I'm not doing anything special with this code btw., just calling bus_alloc_resource() carefully in the right place. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proposed patch to fix VN device (again)
FYI for the list; this has been fixed and committed now. Another problem in vn when backed with swap was found and fixed too. Matthew Dillon wrote: : :Matthew Dillon wrote: :[..] : And, in anycase, I am not going to spend hours putting together a long : involved patch when a simple short patch suffices. If you want to : spend the time to come up with your own patch (that doesn't screw the : pooch in regards to cluster performance!), then I'm all ears, otherwis e : this patch is what is going to go in for the 4.0 release. : :Please hold fire for a bit longer. I have (what I think is) a much cleaner :fix in mind. There is no urgency here, a couple of hours isn't going to :make the slightest difference to the big picture. : :On a side note, as the original author of the changes that lead to this, I :would have thought it would have been appropriate to ask ME directly first :before going public. : :Cheers, :-Peter Your fix looks pretty good, Peter. I'll run it in and test it. I only wish you had come up with it before Poul started going off the deep end. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
the nist port
I can't get the nist port to compile: c++ -g -O2 -Wall -DDO_NIST -DPACKAGE=\"ac3dec\" -DVERSION=\"0.5.5\" -I../../inc -c bitstream.c -o bitstream.o In file included from decode.h:24, from bitstream.c:27: ../../inc/athread.hh: In function `int athr_setschedparam(pthread *, int, sched_param *)': ../../inc/athread.hh:150: implicit declaration of function `int pthread_setschedparam(...)' ../../inc/athread.hh: In function `int athr_getschedparam(pthread *, int *, sched_param *)': ../../inc/athread.hh:151: implicit declaration of function `int pthread_getschedparam(...)' bitstream.c: In function `uint_32 bitstream_get(bitstream_t *, long unsigned int)': bitstream.c:47: warning: unused variable `uint_32 bits_to_go' bitstream.c:46: warning: unused variable `uint_32 bits_read' bitstream.c: At top level: bitstream.c:39: warning: `void bitstream_load(bitstream_t *)' declared `static' but never defined gmake[3]: *** [bitstream.o] Error 1 gmake[3]: Leaving directory `/usr/home/culverk/dl_temp/nist/src/ac3' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/home/culverk/dl_temp/nist/src' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/home/culverk/dl_temp/nist' gmake: *** [all-recursive-am] Error 2 Any help Soren? = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proposed patch to fix VN device (again)
At 8:12 PM +0800 1999/12/28, Peter Wemm wrote: FYI for the list; this has been fixed and committed now. Another problem in vn when backed with swap was found and fixed too. Was the vn problem an issue for 3.x as well? If so, is there any chance of getting this mfc'ed any time soon? -- These are my opinions -- not to be taken as official Skynet policy |o| Brad Knowles, [EMAIL PROTECTED]Belgacom Skynet NV/SA |o| |o| Systems Architect, News FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proposed patch to fix VN device (again)
Brad Knowles wrote: At 8:12 PM +0800 1999/12/28, Peter Wemm wrote: FYI for the list; this has been fixed and committed now. Another problem in vn when backed with swap was found and fixed too. Was the vn problem an issue for 3.x as well? If so, is there any chance of getting this mfc'ed any time soon? No, 3.x doesn't support swap-backed vn devices. Cheers, -Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: more patch for secondary buffer, polling and DMA emulation in pcm
Seigo Tanimura wrote: Ouch, the patch broke Rollemup, so I fixed just now. The URI is the same. Seigo http://people.FreeBSD.org/~tanimura/patches/newmidi/2ndbuf-19991227.diff.gz Great, the sound drivers are working very nicely on my ESS 1868. Does pcm support SoundBlaster WavEffects? Hopefully, nobody will do anything to break the sound drivers (although it may happen). I think I'll make a backup of my /sys/dev source code tree just in case. ;-) - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: the nist port
On Tue, 28 Dec 1999, Kenneth Wayne Culver wrote: I can't get the nist port to compile: the same thing. css-auth builds fine. sincerely, ilya naumov (at work) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: the nist port
It seems Kenneth Wayne Culver wrote: I can't get the nist port to compile: c++ -g -O2 -Wall -DDO_NIST -DPACKAGE=\"ac3dec\" -DVERSION=\"0.5.5\" -I../../inc -c bitstream.c -o bitstream.o In file included from decode.h:24, from bitstream.c:27: ../../inc/athread.hh: In function `int athr_setschedparam(pthread *, int, sched_param *)': ../../inc/athread.hh:150: implicit declaration of function `int pthread_setschedparam(...)' ../../inc/athread.hh: In function `int athr_getschedparam(pthread *, int *, sched_param *)': ../../inc/athread.hh:151: implicit declaration of function `int pthread_getschedparam(...)' bitstream.c: In function `uint_32 bitstream_get(bitstream_t *, long unsigned int)': Uhm, seems like we need to define _POSIX_THREAD_PRIORITY_SCHEDULING now to get the prototypes for these, add: #ifdef __FreeBSD__ #define _POSIX_THREAD_PRIORITY_SCHEDULING #endif At line 80 in inc/athread.hh -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: the nist port
It seems Soren Schmidt wrote: Uhm, seems like we need to define _POSIX_THREAD_PRIORITY_SCHEDULING now to get the prototypes for these, add: #ifdef __FreeBSD__ #define _POSIX_THREAD_PRIORITY_SCHEDULING #endif At line 80 in inc/athread.hh Just to follow up on my self, I've put up a new version that compiles here again at least... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: How to de-select DMA to ad0?
It seems David Gilbert wrote: I've had my share of problems with this drive's DMA abilities. I'm convinced that it has none... even though it probes as such. ad0: NEC Coporation DSE2550A/5DE0314 ATA-0 disk at ata0 as master ad0: ... ad0: 16 secs/int, 1 depth queue, DMA now... when I boot -v, I don't have a chance to write down what it says, but it will hang every time with the following output: ad0: ad-timeout: lost disk contact ata0: resetting drives -- mask=03 status0=50 status1=50 .. And that's it. It never prints out "done" which I see in many of the list messages. Is there a way of disabling DMA on a specific drive? I read a bit of the source, but didn't find any obvious documentation on the issue. There is no way (yet) other than hacking the code, but I'm working on it... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Linux RealPlayer 5.0 working under current?
Does anyone have the linux-realplayer-5.0 port working under -current? I'm running a -current that is a few days old, and have a "Creative ViBRA16C" sound chip. Playing a CDROM using xcdplayer works, but when I try to use realplayer, it just seems to hang. Here are the relevant lines from my boot: sbc0: Creative ViBRA16C at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 9 drq 1,5 on isa0 sbc0: setting card to irq 9, drq 1, 5 pcm0: SB DSP 4.13 on sbc0 I can provide more info if necessary. Thanks, -- Stephen J. Roznowski([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: the nist port
On Tue, 28 Dec 1999, Soren Schmidt wrote: It seems Kenneth Wayne Culver wrote: I can't get the nist port to compile: c++ -g -O2 -Wall -DDO_NIST -DPACKAGE=\"ac3dec\" -DVERSION=\"0.5.5\" -I../../inc -c bitstream.c -o bitstream.o In file included from decode.h:24, from bitstream.c:27: ../../inc/athread.hh: In function `int athr_setschedparam(pthread *, int, sched_param *)': ../../inc/athread.hh:150: implicit declaration of function `int pthread_setschedparam(...)' ../../inc/athread.hh: In function `int athr_getschedparam(pthread *, int *, sched_param *)': ../../inc/athread.hh:151: implicit declaration of function `int pthread_getschedparam(...)' bitstream.c: In function `uint_32 bitstream_get(bitstream_t *, long unsigned int)': Uhm, seems like we need to define _POSIX_THREAD_PRIORITY_SCHEDULING now to get the prototypes for these, add: #ifdef __FreeBSD__ #define _POSIX_THREAD_PRIORITY_SCHEDULING #endif Hey, these _POSIX_THREAD_ definitions used to be in pthread.h. It looks like they were removed from version 1.16 of pthread.h: revision 1.16 date: 1999/12/16 21:53:38; author: jasone; state: Exp; lines: +1 -18 Move POSIX feature constants from pthread.h to unistd.h, as required by 1003.1c-1995. Undefine _POSIX_THREAD_SAFE_FUNCTIONS, since we do not implement all of the necessary interfaces. At least getgrgid_r(), getrnam_r(), getpwuid_r(), getpwnam_r(), getc_unlocked(), getchar_unlocked(), putc_unlocked(), and putchar_unlocked() are missing. Due to a likely typo in 1003.1c-1995, we are not technically allowed to define _POSIX_THREADS without defining _POSIX_THREAD_SAFE_FUNCTIONS, but either way we're non-compliant, so I'm leaving _POSIX_THREADS defined. They're not in unistd.h either. This is a FreeBSD bug. Dan Eischen [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linux RealPlayer 5.0 working under current?
Why bother with 5.0? It cant play any modern streams anyway. http://proforma.real.com/real/player/linuxplayer.html I've been using the Linux G2 player on my -current box for a while now. Video can get a little choppy, and theres an occasional crash, but otherwise its fine. ( This is with both the old sb drivers and the newpcm driver. ) -Irving On Tue, 28 Dec 1999, Stephen J. Roznowski wrote: Date: Tue, 28 Dec 1999 17:24:41 -0500 (EST) From: Stephen J. Roznowski [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Linux RealPlayer 5.0 working under current? Does anyone have the linux-realplayer-5.0 port working under -current? I'm running a -current that is a few days old, and have a "Creative ViBRA16C" sound chip. Playing a CDROM using xcdplayer works, but when I try to use realplayer, it just seems to hang. Here are the relevant lines from my boot: sbc0: Creative ViBRA16C at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 9 drq 1,5 on isa0 sbc0: setting card to irq 9, drq 1, 5 pcm0: SB DSP 4.13 on sbc0 I can provide more info if necessary. Thanks, -- Stephen J. Roznowski([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
SUBMIT: compat.linux.pathmunge
Hello fellow hackers,
I've written up a short patch to add a sysctl to control the appending of
/compat/linux/ to path requests in Linux mode. We had to get ADSM's Linux
client working on FreeBSD so we could do backups of our systems. Luckily
it comes statically linked so all was needed was this sysctl and some
creative redirections (there's a bug in the termio ioctl() emulation
still...) to get it working.
Patch is attached. Alternately you can poke
http://www.freebsd.org/~dwhite/linux.pathmunge.patch. These are against
-current. I have a nasty #ifdef hack for 3.3 that requires Makefile
changes to compile (you want to keep the fixed and unfixed kernel modules
around on 3.3!).
Please let me know if you have comments/suggestions/etc. If no one whines
too badly I'll commit these later this week and finally break my
declaration against making kernel changes. :)
Doug White| FreeBSD: The Power to Serve
[EMAIL PROTECTED] | www.FreeBSD.org
Index: linux_mib.c
===
RCS file: /usr/local/cvs/src/sys/i386/linux/linux_mib.c,v
retrieving revision 1.2
diff -u -r1.2 linux_mib.c
--- linux_mib.c 1999/08/28 02:16:31 1.2
+++ linux_mib.c 1999/12/07 06:33:35
@@ -43,6 +43,7 @@
charpr_osname[LINUX_MAX_UTSNAME];
charpr_osrelease[LINUX_MAX_UTSNAME];
int pr_oss_version;
+int pr_pathmunge;
};
SYSCTL_NODE(_compat, OID_AUTO, linux, CTLFLAG_RW, 0,
@@ -111,6 +112,28 @@
0, 0, linux_sysctl_oss_version, "I",
"Linux OSS version");
+static intlinux_pathmunge = 1;
+
+static int
+linux_sysctl_pathmunge SYSCTL_HANDLER_ARGS
+{
+ int pathmunge;
+ int error;
+
+ pathmunge = linux_get_pathmunge(req-p);
+ error = sysctl_handle_int(oidp, pathmunge, 0, req);
+ if (error || req-newptr == NULL)
+ return (error);
+ error = linux_set_pathmunge(req-p, pathmunge);
+ return (error);
+}
+
+SYSCTL_PROC(_compat_linux, OID_AUTO, pathmunge,
+ CTLTYPE_INT | CTLFLAG_RW | CTLFLAG_PRISON,
+ 0, 0, linux_sysctl_pathmunge, "I",
+ "Linux Path Munge");
+
+
static struct linux_prison *
get_prison(struct proc *p)
{
@@ -226,6 +249,38 @@
lpr-pr_oss_version = oss_version;
else
linux_oss_version = oss_version;
+
+ return (0);
+}
+int
+linux_get_pathmunge(p)
+ struct proc *p;
+{
+ register struct prison *pr;
+ register struct linux_prison *lpr;
+
+ pr = p-p_prison;
+ if (pr != NULL pr-pr_linux != NULL) {
+ lpr = pr-pr_linux;
+ if (lpr-pr_pathmunge)
+ return (lpr-pr_pathmunge);
+ }
+
+ return (linux_pathmunge);
+}
+
+int
+linux_set_pathmunge(p, pathmunge)
+ struct proc *p;
+ int pathmunge;
+{
+ register struct linux_prison *lpr;
+
+ lpr = get_prison(p);
+ if (lpr != NULL)
+ lpr-pr_pathmunge = pathmunge;
+ else
+ linux_pathmunge = pathmunge;
return (0);
}
Index: linux_mib.h
===
RCS file: /usr/local/cvs/src/sys/i386/linux/linux_mib.h,v
retrieving revision 1.2
diff -u -r1.2 linux_mib.h
--- linux_mib.h 1999/08/28 02:16:32 1.2
+++ linux_mib.h 1999/12/07 05:22:18
@@ -1,3 +1,4 @@
+
/*-
* Copyright (c) 1999 Marcel Moolenaar
* All rights reserved.
@@ -39,5 +40,8 @@
intlinux_get_oss_version __P((struct proc *p));
intlinux_set_oss_version __P((struct proc *p, int oss_version));
+
+intlinux_get_pathmunge __P((struct proc *p));
+intlinux_set_pathmunge __P((struct proc *p, int pathmunge));
#endif /* _LINUX_MIB_H_ */
Index: linux_util.c
===
RCS file: /usr/local/cvs/src/sys/i386/linux/linux_util.c,v
retrieving revision 1.8
diff -u -r1.8 linux_util.c
--- linux_util.c1999/08/28 00:45:25 1.8
+++ linux_util.c1999/12/08 05:22:49
@@ -38,6 +38,7 @@
#include sys/vnode.h
#include i386/linux/linux_util.h
+#include i386/linux/linux_mib.h
const char linux_emul_path[] = "/compat/linux";
@@ -69,8 +70,22 @@
buf = (char *) malloc(MAXPATHLEN, M_TEMP, M_WAITOK);
*pbuf = path;
- for (ptr = buf; (*ptr = *prefix) != '\0'; ptr++, prefix++)
- continue;
+ /*
+* Look at the compat.linux.pathmunge sysctl to determine
+* whether to add the linux_emul_path on the front of the
+* requested file. Software that does tree walks, such
+* as backup clients, get locked into the /compat/linux
+* subtree if this is set. Setting the sysctl to 0
+* makes Linux apps access files like any other, but must
+* be statically linked or they'll never find their libs.
+*/
+
+ if(linux_get_pathmunge(p)) {
+ for (ptr = buf;
Re: the nist port
They're in sys/unistd.h, which is included by unistd.h. That should be just fine, and that location appears to be consistent with our other POSIX macro definitions. Ahh, good. I didn't have them because I wasn't up to date. So the question is now, why wasn't the nist port picking them up? Dan Eischen [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 . 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]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc compile error
On Sun, Dec 26, 1999 at 12:13:42PM -0500, Donn Miller wrote: I get similar errors trying to compile aview from ports. I just updated my ports tree, so that can't be the problem. See the attached make.log. There's something about not allowing access to the cx register. ... sstring.h:493: fixed or forbidden register 2 (cx) was spilled for class CREG. These are easy to fix. Please use `send-pr' to submit a PR and hopefully I can get to it. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
-current and IPv6
Hi Lists, How are the implementation of IPv6 in FreeBSD 4.0? Is it available? Is it stable? What is better: use FreeBSD 3.4 with Kame or FreeBSD 4.0? Thanks, Luciano Rabelo 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
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 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SUBMIT: compat.linux.pathmunge
On Tue, 28 Dec 1999, Doug White wrote: Hello fellow hackers, I've written up a short patch to add a sysctl to control the appending of /compat/linux/ to path requests in Linux mode. We had to get ADSM's Linux client working on FreeBSD so we could do backups of our systems. Luckily it comes statically linked so all was needed was this sysctl and some creative redirections (there's a bug in the termio ioctl() emulation still...) to get it working. Patch is attached. Alternately you can poke http://www.freebsd.org/~dwhite/linux.pathmunge.patch. These are against -current. I have a nasty #ifdef hack for 3.3 that requires Makefile changes to compile (you want to keep the fixed and unfixed kernel modules around on 3.3!). Please let me know if you have comments/suggestions/etc. If no one whines too badly I'll commit these later this week and finally break my declaration against making kernel changes. :) Good idea that... Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org Index: linux_mib.c === RCS file: /usr/local/cvs/src/sys/i386/linux/linux_mib.c,v retrieving revision 1.2 diff -u -r1.2 linux_mib.c --- linux_mib.c 1999/08/28 02:16:31 1.2 +++ linux_mib.c 1999/12/07 06:33:35 @@ -43,6 +43,7 @@ charpr_osname[LINUX_MAX_UTSNAME]; charpr_osrelease[LINUX_MAX_UTSNAME]; int pr_oss_version; +int pr_pathmunge; bruce white space inconsistancy /bruce }; SYSCTL_NODE(_compat, OID_AUTO, linux, CTLFLAG_RW, 0, @@ -111,6 +112,28 @@ 0, 0, linux_sysctl_oss_version, "I", "Linux OSS version"); 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
On Tue, 28 Dec 1999, Amancio Hasty wrote: 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. Typically this empty space would contain the output of the build failure, more details, or even a patch. You might want to find out why your mailer is thrashing it. 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. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: the nist port
It seems Daniel Eischen wrote: They're in sys/unistd.h, which is included by unistd.h. That should be just fine, and that location appears to be consistent with our other POSIX macro definitions. Ahh, good. I didn't have them because I wasn't up to date. So the question is now, why wasn't the nist port picking them up? Because unistd.h is not included as linux/solaris/etc doesn't need that. I've put in yet another ifdef __FreeBSD__ to deal with it, sigh -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
mmaping /dev/dsp problems
Hello,
I'm trying to get the quake 1 source to compile and work under freebsd with glx.
Most of the graphics parts work, and I can play, but I can't seem to get it to
mmap the dsp dma buffer like it wants to.
I have ripped out part of the code to demonstrate the problem. All I had to
change to get it to compile this was to include machine/soundcard.h instead of
linux/soundcard.h, but that doesn't seem to be enough to get it to work.
I'm running -current with newpcm as of Dec 13, I know it's not the latest, but
not much has changed in the dsp code lately. I'll build a new world tomorrow,
and try it out.
I have attached the files snd_linux.c sound.h
When I run snd_linux I get
opening /dev/dsp
audio_fd /dev/dsp=3
about to map 63488 bytes to /dev/dsp
shm-buffer=280eb000
Segmentation fault (core dumped)
bash-2.02$
gdb has this to say about shm-buffer (what mmap returns)
$3 = (
unsigned char *) 0x280eb000 Error reading address 0x280eb000: Bad address
Thanks, for any help.
-Charlie
--
Charles Anderson[EMAIL PROTECTED]
No quote, no nothin'
/*
Copyright (C) 1996-1997 Id Software, Inc.
This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
*/
#include unistd.h
#include fcntl.h
#include stdlib.h
#include sys/types.h
#include sys/ioctl.h
#include sys/mman.h
#include sys/shm.h
#include sys/wait.h
#include machine/soundcard.h
#include stdio.h
#include "sound.h"
int audio_fd;
int snd_inited;
static int tryrates[] = { 11025, 22051, 44100, 8000 };
#define Con_Printf printf
dma_t *shm;
qboolean SNDDMA_Init(void)
{
dma_t sn;
int rc;
int fmt;
int tmp;
int i;
char *s;
struct audio_buf_info info;
int caps;
snd_inited = 0;
// open /dev/dsp, confirm capability to mmap, and get size of dma buffer
Con_Printf("opening /dev/dsp\n");
audio_fd = open("/dev/dsp", O_RDWR);
if (audio_fd 0)
{
perror("/dev/dsp");
Con_Printf("Could not open /dev/dsp\n");
return 0;
}
Con_Printf("audio_fd /dev/dsp=%d\n", audio_fd);
rc = ioctl(audio_fd, SNDCTL_DSP_RESET, 0);
if (rc 0)
{
perror("/dev/dsp");
Con_Printf("Could not reset /dev/dsp\n");
close(audio_fd);
return 0;
}
if (ioctl(audio_fd, SNDCTL_DSP_GETCAPS, caps)==-1)
{
perror("/dev/dsp");
Con_Printf("Sound driver too old\n");
close(audio_fd);
return 0;
}
if (!(caps DSP_CAP_TRIGGER) || !(caps DSP_CAP_MMAP))
{
Con_Printf("Sorry but your soundcard can't do this\n");
close(audio_fd);
return 0;
}
if (ioctl(audio_fd, SNDCTL_DSP_GETOSPACE, info)==-1)
{
perror("GETOSPACE");
Con_Printf("Um, can't do GETOSPACE?\n");
close(audio_fd);
return 0;
}
shm = sn;
shm-splitbuffer = 0;
// set sample bits speed
s = getenv("QUAKE_SOUND_SAMPLEBITS");
if (s) shm-samplebits = atoi(s);
/* else if ((i = COM_CheckParm("-sndbits")) != 0)
shm-samplebits = atoi(com_argv[i+1]); */
if (shm-samplebits != 16 shm-samplebits != 8)
{
ioctl(audio_fd, SNDCTL_DSP_GETFMTS, fmt);
if (fmt AFMT_S16_LE) shm-samplebits = 16;
else if (fmt AFMT_U8) shm-samplebits = 8;
}
s = getenv("QUAKE_SOUND_SPEED");
if (s) shm-speed = atoi(s);
/* else if ((i = COM_CheckParm("-sndspeed")) != 0)
shm-speed = atoi(com_argv[i+1]); */
else
{
for (i=0 ; isizeof(tryrates)/4 ; i++)
if (!ioctl(audio_fd, SNDCTL_DSP_SPEED, tryrates[i])) break;
shm-speed = tryrates[i];
}
s = getenv("QUAKE_SOUND_CHANNELS");
if (s) shm-channels = atoi(s);
/* else if ((i = COM_CheckParm("-sndmono")) != 0)
shm-channels = 1;
else if ((i = COM_CheckParm("-sndstereo")) != 0)
shm-channels = 2; */
else shm-channels = 2;
shm-samples = info.fragstotal * info.fragsize / (shm-samplebits/8);
shm-submission_chunk = 1;
// memory map the dma buffer
Con_Printf("about to map %d bytes to /dev/dsp\n", info.fragstotal * info.fragsize);
shm-buffer = (unsigned char *)
RE: mmaping /dev/dsp problems
On 29-Dec-99 Charles Anderson wrote: Hello, I'm trying to get the quake 1 source to compile and work under freebsd with glx. 'me too' :) I have it working, it has some 'interesting' colour problems tho.. And it hangs after about 10 seconds of playing around. (Its killable though) Speaking of your mmap() problem.. When I try quake and the mmap sample program they get stuck in pcmflush forever :( --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum 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. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [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
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]
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
Amancio Hasty wrote: 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. No, it is not, because we can't *get* XFree86 3.9.xxx -current, so we cannot reproduce it, can we? You either need to give us enough to build that part, or provide a preprocessed file so we can feed the backends directly, or fix it yourself. Cheers, -Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current and IPv6
Hi Lists, How are the implementation of IPv6 in FreeBSD 4.0? Is it available? Is it stable? The work on the current is still going on. Followings are already committed, and seems to be working well. -most of IPv6 extensions in kernel(tcp for IPv6 and IPv6 multicasting not yet) -IPsec in kernel -libc update -basic tools(ifconfig, route, netstat) -several udp and raw apps for IPv6 Now following patch is under review on freebsd-arch and cvs-committers. -tcp for IPv6 And following patch will be made for review soon. -libipsec and several ipsec related apps Then followings will be prepared. -IPv6 multicasting for kernel and apps -tcp apps for IPv6 -ppp for IPv6 -several library updates for IPv6 -many ports for IPv6 What is better: use FreeBSD 3.4 with Kame or FreeBSD 4.0? Enough functionality is available now only on FreeBSD 3.4 with Kame. And other differencies are, - on-going merging on FreeBSD4.0 is based on KAME 19991101 SNAP, and some add on bug fixes. So FreeBSD 3.4 with Kame has newer changes based on KAME environment. (also might have newer bugs ;-) - I found some FreeBSD 3.x with Kame bugs on merging work, and fixed them on the current. Significant ones are committed to KAME repository soon, but small things might be delayed, because now I am more concentrated on 4.0 merging work. Yoshinobu Inoue Luciano Rabelo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
